dbcve.org
Lotus DominoApplication · Ibm

CVE-2013-0489

MEDIUM · 6.0 CVSS v2.0 Published 2013-03-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
66/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Cross-site request forgery (CSRF) vulnerability in webadmin.nsf (aka the Web Administrator client) in IBM Domino 8.5.x allows remote authenticated users to hijack the authentication of administrators.

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 confidence

Cross-site request forgery (CSRF) vulnerability in webadmin.nsf (Web Administrator client) in IBM Domino 8.5.x allows remote authenticated users to hijack the authentication of administrators by tricking them into executing unintended actions through malicious requests.

MitigationImplement anti-CSRF tokens or validation mechanisms in webadmin.nsf forms and actions, and consider restricting webadmin.nsf access to trusted IP addresses or requiring stronger authentication for administrative functions.

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
Lotus DominoApplication
Affected:= 8.5.0= 8.5.0.1= 8.5.1= 8.5.1.1= 8.5.1.2= 8.5.1.3= 8.5.1.4= 8.5.1.5= 8.5.2.0= 8.5.2.1= 8.5.2.2= 8.5.2.3

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify IBM Domino version
    Run 'nsh -version' or check the Domino program directory for version files, or query the Domino server console with 'show version'
    Affected if Installed version matches 8.5.0 through 8.5.2.3 (any of the listed affected versions)
  2. Locate webadmin.nsf
    Search the Domino data directory for webadmin.nsf file, typically found in the Domino\data folder
    Affected if webadmin.nsf file exists on the server
  3. Verify Web Administrator client accessibility
    Attempt to access http(s)://<server>/webadmin.nsf in a web browser or via curl from an authorized network
    Affected if The URL responds and displays the Web Administrator login or console (even if authentication is required)

A user is affected if they run any IBM Domino 8.5.0-8.5.2.3 version AND have the webadmin.nsf Web Administrator client accessible on the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens or validation mechanisms in webadmin.nsf forms and actions, and consider restricting webadmin.nsf access to trusted IP addresses or requiring stronger authentication for administrative functions.

Fix this in Lotus Domino Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-0489 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-0489 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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