CVE-2007-5371
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMultiple SQL injection vulnerabilities in mutate_content.dynamic.php in MODx 0.9.6 allow remote attackers to execute arbitrary SQL commands via the (1) documentDirty or (2) modVariables parameter.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSQL injection vulnerabilities in MODx 0.9.6's mutate_content.dynamic.php allow remote attackers to execute arbitrary SQL commands through the documentDirty and modVariables parameters. This is a classic SQL injection flaw where user-supplied input is not properly sanitized before being used in database queries.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 0.9.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify MODx version is 0.9.6Check the version string in your MODx installation by reviewing the configuration file (likely manager/includes/config.php or similar version file) or accessing the MODx admin dashboard About sectionAffected if The installed version is exactly 0.9.6 (note: only this specific version is affected)
-
Confirm mutate_content.dynamic.php existsLocate the file mutate_content.dynamic.php in the manager directory of your MODx installation (typically /manager/actions/mutate_content.dynamic.php) and verify it is present on the serverAffected if The file exists in the expected path and the application is running MODx 0.9.6
-
Check for unpatched parameter handlingReview the source code of mutate_content.dynamic.php and search for direct use of $_REQUEST['documentDirty'] or $_REQUEST['modVariables'] in SQL query contexts without sanitization functions like mysql_escape_string or parameterized queriesAffected if The code shows these parameters are used directly in SQL queries without input sanitization
-
Audit database user privilegesCheck the database user configured in MODx's config.php - verify if it has only the minimum required privileges (not DROP, GRANT, or file privileges)Affected if The database user has excessive privileges beyond SELECT, INSERT, UPDATE, DELETE
You are affected if your MODx installation is exactly version 0.9.6 and the mutate_content.dynamic.php file exists with unpatched SQL handling of documentDirty or modVariables parameters.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade MODx to a patched version beyond 0.9.6, or apply vendor-provided patches for these specific parameters. As a temporary control, implement input validation and consider WAF deployment to block SQL injection attempts.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-5371 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2007-5371 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data