CVE-2012-2128
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 · uneditedCross-site request forgery (CSRF) vulnerability in doku.php in DokuWiki 2012-01-25 Angua allows remote attackers to hijack the authentication of administrators for requests that add arbitrary users. NOTE: this issue has been disputed by the vendor, who states that it is resultant from CVE-2012-2129: "the exploit code simply uses the XSS hole to extract a valid CSRF token."
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 confidenceCSRF vulnerability in DokuWiki's doku.php allows remote attackers to hijack administrator authentication and add arbitrary users. The vendor disputes this as a standalone flaw, claiming it is resultant from CVE-2012-2129 (XSS) which enables extraction of valid CSRF tokens.
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= 2012-01-25CVSS 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.
-
Identify DokuWiki versionCheck the version file or meta information in the DokuWiki installation. Common locations include a version.php file or the DokuWiki footer/meta in the admin interface. Compare the installed version to the affected version 2012-01-25.Affected if The installed version is exactly 2012-01-25 (older or newer versions are not affected by this specific CVE).
-
Locate doku.phpIdentify if doku.php exists in the DokuWiki web root directory. This is the main entry point where the CSRF vulnerability exists.Affected if doku.php is present and accessible in the web-accessible directory.
-
Verify admin access to user managementAccess the administrator interface and navigate to the user management section (typically at /doku.php?id=admin:users or similar admin routes). Check if the admin user management functions are accessible.Affected if The admin user management functions are accessible without requiring additional CSRF token validation beyond what can be extracted via the XSS flaw.
-
Check for CSRF token validation on admin actionsInspect the admin user management functionality in doku.php to determine if POST requests for adding/modifying users include and validate CSRF tokens server-side.Affected if The admin user management functions lack proper CSRF token validation or allow token extraction via the XSS vulnerability (CVE-2012-2129).
You are affected if you are running DokuWiki version 2012-01-25 AND the admin user management functions in doku.php lack proper CSRF token validation, making them vulnerable to token extraction via the related XSS flaw.
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 dataFix the underlying XSS vulnerability (CVE-2012-2129) and implement proper CSRF token validation on admin user management functions to prevent token extraction and forged requests.
- 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-2012-2128 — 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-2012-2128 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