CVE-2013-4050
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 webadmin.nsf in Domino Web Administrator in IBM Domino 8.5 and 9.0 allows remote authenticated users to hijack the authentication of unspecified victims 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 · moderate confidenceCross-site request forgery (CSRF) vulnerability in IBM Domino Web Administrator (webadmin.nsf) allows authenticated remote attackers to hijack the authentication of other users by tricking them into submitting malicious requests. The vulnerability affects Domino versions 8.5 and 9.0.
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= 8.5.0= 9.0.0.0CVSS 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
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:S/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 IBM Domino installation and versionCheck the Domino version by running 'show version' at the Domino server console, or inspect the installed Domino binaries and readme files in the installation directoryAffected if The installed version is exactly 8.5.0 or 9.0.0.0 (note the equal signs indicate these specific versions)
-
Verify webadmin.nsf database existsLocate the webadmin.nsf file in the Domino data directory (typically in the data/domino or data directory where Domino is installed)Affected if The webadmin.nsf database file exists and is accessible on the server
-
Confirm Web Administrator HTTP task is enabledAt the Domino console, run 'show tasks' to list running tasks and verify the 'Web Admin' or 'HTTP' task is active, or check the notes.ini for 'ServerTasks=' configuration that includes webadminAffected if The HTTP task and Web Administrator functionality are enabled and running
-
Check if HTTP interface is accessibleAttempt to access the webadmin.nsf via HTTP from a browser: http://servername/webadmin.nsf (or test using curl/telnet to port 80/443)Affected if The webadmin.nsf is reachable over HTTP/HTTPS without requiring authentication, or is reachable after authentication
-
Confirm user authentication methodReview the ACL (Access Control List) settings of webadmin.nsf and server configuration to determine if users can authenticate via webAffected if Web authentication is enabled and users can authenticate to the Web Administrator interface
You are affected if your IBM Domino server runs version 8.5.0 or 9.0.0.0 specifically, the webadmin.nsf database exists and is accessible, and the Web Administrator HTTP interface is enabled.
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 dataApply IBM Domino security patches for versions 8.5.x and 9.0.x, or upgrade to a later patched version. For custom applications, implement anti-CSRF tokens in forms and requests.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-4050 — 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-2013-4050 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