CVE-2006-2259: SQL injection vulnerability in Logon.asp in MaxxSchedule 1.0 allows remote attackers to execute arbitrary SQL

This month

HIGH 7.5DOWNGRADE

CVE-2006-2259 is a high-severity flaw (CVSS 7.5) affecting maxxschedule. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

SQL injection vulnerability in Logon.asp in MaxxSchedule 1.0 allows remote attackers to execute arbitrary SQL commands via the txtLogon parameter.

Why this priority

High severity

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.5 (High)
EPSS exploit chance	1.3% (top 29%)
CISA exploited list	No
Weakness	CWE-89
Published	2006-05-09
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: maxxcode

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2006-05-09 10:02 UTCPublished CVE record published
2026-06-16 22:24 UTCUpdated Record last modified

maxxcode maxxschedule DOWNGRADE

Affected: 1.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.0

1. Check installed version

apt-cache policy maxxschedule || rpm -q maxxschedule || maxxschedule --version

2. No fixed release: DOWNGRADE to a release before 1.0 (Debian / Ubuntu)

apt-cache madison maxxschedule sudo apt install maxxschedule=<VERSION_BEFORE_1.0> sudo apt-mark hold maxxschedule

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list maxxschedule sudo dnf downgrade maxxschedule-<VERSION_BEFORE_1.0> sudo dnf versionlock add maxxschedule

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2006-2259?

maxxschedule: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2006-2259 being exploited?

CVE-2006-2259 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2006-2259 affect?

CVE-2006-2259 affects maxxschedule. Severity is high (CVSS 7.5). SQL injection vulnerability in Logon.asp in MaxxSchedule 1.0 allows remote attackers to execute arbitrary SQL commands via the txtLogon parameter.

How urgent is CVE-2006-2259?

Priority 44/100. High severity

Related CVEs

CVE-2006-2258 LOW 2.6 DOWNGRADE Cross-site scripting (XSS) vulnerability in Logon.asp in MaxxSchedule 1.0 allows remote attackers to inject ar

References

← Back to latest CVEs