CVE-2014-8762
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 · uneditedThe ajax_mediadiff function in DokuWiki before 2014-05-05a allows remote attackers to access arbitrary images via a crafted namespace in the ns 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 · moderate confidenceThe ajax_mediadiff function in DokuWiki before version 2014-05-05a contains an access control bypass vulnerability in the ns parameter. Attackers can craft malicious namespace values to access arbitrary images outside the intended media directory scope, effectively allowing unauthorized file system access to image files.
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<= 2013-12-08CVSS 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 DokuWiki versionCheck the VERSION file in the DokuWiki root directory, or view the page source of any DokuWiki page to find the version number in the generator meta tagAffected if Version is 2013-12-08 or earlier (the last vulnerable release)
-
Locate the vulnerable ajax.php fileFind the ajax.php file in the DokuWiki root installation directory - this file contains the ajax_mediadiff functionAffected if The ajax.php file exists and contains the ajax_mediadiff function definition without proper ns parameter validation
-
Examine the ajax_mediadiff functionOpen the ajax.php file and search for the ajax_mediadiff function - inspect the code handling the ns parameter to verify if input validation is presentAffected if The function does not properly validate or sanitize the ns parameter before using it in file path operations
-
Verify media directory access controlsCheck the conf/local.php or conf/local.protected.php for media permissions settings and verify if the ACL system properly restricts media accessAffected if ACL settings allow public or unauthenticated access to the ajax_mediadiff function or media namespace operations
A DokuWiki installation is affected if it is version 2013-12-08 or earlier and the ajax_mediadiff function in ajax.php lacks proper input validation for the ns parameter, allowing path traversal to access images outside intended directories.
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 DokuWiki to version 2014-05-05a or later which includes proper input validation for the ns parameter. If immediate upgrading is not feasible, restrict access to the ajax_mediadiff function via web server access controls or firewall rules.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-8762 — 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-2014-8762 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