CVE-2020-14240
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 · uneditedHCL Notes versions previous to releases 9.0.1 FP10 IF8, 10.0.1 FP6 and 11.0.1 FP1 is susceptible to a Stored Cross-site Scripting (XSS) vulnerability. An attacker could use this vulnerability to execute script in a victim's Web browser within the security context of the hosting Web site and/or steal the victim's cookie-based authentication credentials.
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 confidenceStored Cross-site Scripting (XSS) vulnerability in HCL Notes web interface allows attackers to inject malicious scripts that persist on the server and execute in victims' browsers when viewing affected content, potentially enabling session hijacking through stolen cookie-based authentication credentials.
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>= 9.0, <= 9.0.1>= 10.0, <= 10.0.1>= 11.0, <= 11.0.1= 9.0.1= 10.0.1CVSS 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
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 HCL Notes versionOpen the HCL Notes client and go to Help > About HCL Notes, or check the version via the Domino Administrator client. On Windows, the version may also be visible in Add/Remove Programs or the program properties.Affected if The version number falls within 9.0.x (except FP10 IF8+), 10.0.x (except FP6+), or 11.0.x (except FP1+) - specifically versions 9.0, 9.0.1, 10.0, 10.0.1, 11.0, and 11.0.1 base releases are affected.
-
Confirm HCL Notes web interface (iNotes) is enabledCheck the Domino server document in the Domino Directory. Under Server > Internet Protocols > HTTP, verify that the 'iNotes Redirect' or 'iNotes' HTTP extension is enabled, or check if HTTP task is running and serving web requests on ports 80/443.Affected if The iNotes/webmail HTTP task is active and accessible, as this is the attack vector for the stored XSS vulnerability.
-
Verify webmail configuration allows user content renderingExamine the Domino server's notes.ini settings or the iNotes configuration document for settings related to HTML rendering of user-submitted content in mail and calendar entries.Affected if HTML rendering of user content is enabled in the web interface configuration, allowing stored scripts to execute when other users view the affected content.
If the HCL Notes version is 9.0, 9.0.1, 10.0, 10.0.1, 11.0, or 11.0.1 without the respective Fix Packs (FP10 IF8 for 9.x, FP6 for 10.x, FP1 for 11.x), AND the iNotes web interface is enabled and accessible, the environment is vulnerable to stored XSS attacks.
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 the vendor-supplied fixes by upgrading to HCL Notes 9.0.1 FP10 IF8, 10.0.1 FP6, or 11.0.1 FP1 as appropriate for your deployment.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14240 — 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-2020-14240 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