dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-9007

MEDIUM · 5.5 CVSS v4.0 Published 2026-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 5 weeks old

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
Improper neutralization of input during web page generation ('cross-site scripting') vulnerability in HCL Notes from HCL Software allows reflected Cross-Site Scripting (XSS).  Successful exploitation allows an attacker to execute arbitrary JavaScript in the context of another user. This issue affects HCL Notes: Release 12.0.2FP5HF8 on Linux 4.18.0-553.52.1.El8_10.X64_64#1.

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

Reflected cross-site scripting (XSS) vulnerability in HCL Notes allows injection of malicious JavaScript through unsanitized user input that gets reflected in web page generation. Attackers can trick users into clicking crafted links to execute arbitrary JavaScript in their browser context.

MitigationApply available vendor patches for HCL Notes 12.0.2FP5HF8. Until patched, users should avoid clicking untrusted links and organizations may consider disabling JavaScript rendering in Notes client web preview features.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Low
Privileges
None
Authentication
X
User interaction
A
Scope
X

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Verify HCL Notes installation
    Check for HCL Notes installation directory (commonly at C:\Program Files\HCL\Notes or C:\Program Files (x86)\HCL\Notes on Windows, or /opt/hcl/notes on Linux)
    Affected if HCL Notes is installed on the system
  2. Determine installed Notes version
    Open HCL Notes client, go to File > HCL Notes > About or check the notes.ini file in the Notes data directory for Version= or Release= entries
    Affected if The version is 12.0.2 FP5 or earlier without the HF8 hotfix, or falls within any affected version range that remains unpatched
  3. Confirm web preview feature is enabled
    In Notes client, go to File > Preferences > Web Preview (or check notes.ini for WebPreview=1 setting)
    Affected if Web preview feature is enabled and users can view web content within Notes
  4. Check JavaScript rendering in web preview
    In Notes client preferences under Web Preview, verify if JavaScript rendering is allowed (notes.ini may contain EnableJavaScript=1)
    Affected if JavaScript rendering is enabled in the web preview settings

User is affected if HCL Notes is installed with an unpatched version and web preview features with JavaScript rendering are enabled, allowing unsanitized input to be reflected in generated web pages.

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

Apply available vendor patches for HCL Notes 12.0.2FP5HF8. Until patched, users should avoid clicking untrusted links and organizations may consider disabling JavaScript rendering in Notes client web preview features.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9007 — 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-2026-9007 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