CVE-2010-0289
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 cross-site request forgery (CSRF) vulnerabilities in the ACL Manager plugin (plugins/acl/ajax.php) in DokuWiki before 2009-12-25c allow remote attackers to hijack the authentication of administrators for requests that modify access control rules, and other unspecified requests, via unknown vectors.
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 confidenceCross-site request forgery vulnerabilities in the DokuWiki ACL Manager plugin (plugins/acl/ajax.php) allow remote attackers to trick authenticated administrators into modifying access control rules without their consent, by exploiting the absence of CSRF token validation in the ajax.php endpoint.
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<= release_2009-02-14= 2004-07-04= 2004-07-07= 2004-07-12= 2004-07-21= 2004-07-25= 2004-08-08= 2004-08-15a= 2004-08-22= 2004-09-12= 2004-09-25= 2004-09-30CVSS 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 versionLocate the DokuWiki version file (typically named VERSION in the root directory) or check the version constant in inc/init.phpAffected if The installed version matches or predates release_2009-02-14, or equals any of these: 2004-07-04, 2004-07-07, 2004-07-12, 2004-07-21, 2004-07-25, 2004-08-08, 2004-08-15a, 2004-08-22, 2004-09-12, 2004-09-25, 2004-09-30
-
Verify ACL Manager plugin existsCheck for the presence of the acl plugin directory at plugins/acl/ and confirm the ajax.php file exists within itAffected if The plugins/acl/ajax.php file is present on the server
-
Inspect CSRF protection in ajax.phpOpen plugins/acl/ajax.php and search for CSRF token validation logic (look for references to 'csrf', 'token', 'validate', or 'check' functions related to request verification)Affected if No CSRF token validation routine is found in the ajax.php file, meaning requests lack anti-CSRF protection
-
Confirm administrator authentication is in useReview server logs or ACL plugin configuration to determine if administrators have been logging in and using the ACL Manager interfaceAffected if Authenticated administrator sessions exist, as the CSRF attack requires tricking a logged-in admin
You are affected if your DokuWiki version is listed in the affected versions AND the plugins/acl/ajax.php file exists AND lacks CSRF token validation code.
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 2009-12-25c or later which contains the patched ACL Manager plugin with CSRF protection, or implement anti-CSRF tokens in the plugin's ajax.php handlers.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-0289 — 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-0289 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