CVE-2014-8761
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 · uneditedinc/template.php in DokuWiki before 2014-05-05a only checks for access to the root namespace, which allows remote attackers to access arbitrary images via a media file details ajax call.
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 inc/template.php file in DokuWiki versions before 2014-05-05a contains an access control flaw where namespace permission checks only validate access to the root namespace rather than the specific namespace containing the requested media file. This allows remote attackers to bypass intended access restrictions and view arbitrary images via the media file details ajax call by manipulating namespace parameters.
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 installed DokuWiki versionCheck the VERSION file in the DokuWiki root directory, or look at the meta header in any DokuWiki page source for the version stringAffected if The installed version is 2013-12-08 or earlier (any version <= 2013-12-08)
-
Verify vulnerable file existsConfirm the file inc/template.php exists in the DokuWiki installation directoryAffected if The file exists and the version check shows a vulnerable version
-
Check media manager ajax functionality exposureDetermine if the media file details ajax endpoint is accessible by checking if the wiki allows unauthenticated or lower-privileged access to media file operationsAffected if The media ajax functionality is accessible to users who should not have access to certain namespace media files
-
Inspect namespace access control configurationReview DokuWiki ACL configuration (typically in conf/acl.auth.php) to determine if media files are protected by namespace-level permissionsAffected if ACL rules only protect at the root namespace level or do not properly restrict media access within specific namespaces
If running DokuWiki version 2013-12-08 or earlier and the media file details ajax functionality is accessible, the namespace permission bypass vulnerability is present.
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 DokuWiki 2014-05-05a or later which implements proper namespace-level access control validation. If immediate upgrade is not possible, consider restricting network access to the wiki or implementing additional access controls at the web server level.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-8761 — 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-8761 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