CVE-2009-1764: SQL injection vulnerability in inc/ajax.asp in MaxCMS 2.0 allows remote attackers to execute arbitrary SQL com

This month

HIGH 7.5DOWNGRADE

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

SQL injection vulnerability in inc/ajax.asp in MaxCMS 2.0 allows remote attackers to execute arbitrary SQL commands via the id parameter in a digg action.

Why this priority

High severity
Public exploit reference

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

Risk facts

CVSS score	7.5 (High)
EPSS exploit chance	1.0% (top 38%)
CISA exploited list	No
Weakness	CWE-89
Published	2009-05-22
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: bokecc

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

Am I affected?

Timeline

2009-05-22 18:30 UTCPublished CVE record published
2026-06-16 23:08 UTCUpdated Record last modified

bokecc maxcms DOWNGRADE

Affected: 2.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.0

1. Check installed version

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

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

apt-cache madison maxcms sudo apt install maxcms=<VERSION_BEFORE_2.0> sudo apt-mark hold maxcms

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

dnf --showduplicates list maxcms sudo dnf downgrade maxcms-<VERSION_BEFORE_2.0> sudo dnf versionlock add maxcms

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.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Exploit-DB: MaxCMS 2.0 - '/inc/ajax.asp' SQL Injection

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-2009-1764?

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

Is CVE-2009-1764 being exploited?

CVE-2009-1764 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-2009-1764 affect?

CVE-2009-1764 affects maxcms. Severity is high (CVSS 7.5). SQL injection vulnerability in inc/ajax.asp in MaxCMS 2.0 allows remote attackers to execute arbitrary SQL commands via the id parameter in a digg action.

How urgent is CVE-2009-1764?

Priority 47/100. High severity; Public exploit reference

Related CVEs

CVE-2009-3426 MEDIUM 6.8 DOWNGRADE PHP remote file inclusion vulnerability in includes/file_manager/special.php in MaxCMS 3.11.20b allows remote
CVE-2009-3425 MEDIUM 5.0 DOWNGRADE Directory traversal vulnerability in includes/inc.thcms_admin_dirtree.php in MaxCMS 3.11.20b allows remote att
CVE-2009-3424 MEDIUM 6.8 DOWNGRADE Multiple PHP remote file inclusion vulnerabilities in MaxCMS 3.11.20b, when register_globals is enabled, allow
CVE-2009-1818 HIGH 7.5 DOWNGRADE SQL injection vulnerability in admin/admin_manager.asp in MaxCMS 2.0 allows remote attackers to execute arbitr

References

← Back to latest CVEs