CVE-2010-3930
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 · uneditedDirectory traversal vulnerability in MODx Evolution 1.0.4 and earlier allows remote attackers to read arbitrary files via unspecified vectors related to AjaxSearch, a different vulnerability than CVE-2010-1427.
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 · moderate confidenceDirectory traversal vulnerability in MODx Evolution 1.0.4 and earlier allows remote attackers to read arbitrary files on the server via the AjaxSearch component through path traversal sequences (e.g., ../../../').
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<= 1.0.4= 0.9.0= 0.9.1= 0.9.2.1= 0.9.5= 0.9.6= 0.9.6.1= 0.9.6.2= 1.0.2= 1.0.3CVSS 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
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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.
-
Identify if Modxcms Evolution is installedCheck your web server for Modxcms Evolution installation directories or check version file in the installation rootAffected if Modxcms Evolution is present on the server
-
Determine installed Modxcms Evolution versionLocate the version file or index file in the Modxcms installation directory and read the version numberAffected if The installed version matches <= 1.0.4, or is one of: 0.9.0, 0.9.1, 0.9.2.1, 0.9.5, 0.9.6, 0.9.6.1, 0.9.6.2, 1.0.2, 1.0.3, 1.0.4
-
Check if AjaxSearch component existsLook for the AjaxSearch component directory or files within the Modxcms installation, typically under assets/snippets/ or similar component directoriesAffected if The AjaxSearch component is present in the installation
-
Verify AjaxSearch is accessible via webAttempt to access the AjaxSearch component endpoint or check if it is loaded and functional on the siteAffected if The AjaxSearch component is accessible and operational on the site
-
Test for directory traversal vulnerabilityIf AjaxSearch is accessible, send a test request with path traversal sequences (such as ../../../) to the search parameter to observe if arbitrary file read is possibleAffected if The server responds with contents of files outside the intended directory
The environment is affected if Modxcms Evolution version 1.0.4 or earlier is installed AND the AjaxSearch component is present and accessible, allowing path traversal attacks to read arbitrary files.
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 to a patched version of MODx Evolution; if immediate upgrade is not feasible, disable or restrict access to the AjaxSearch component and/or implement input validation to sanitize file path parameters.
- 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-2010-3930 — 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-2010-3930 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