dbcve.org
Hcl InotesApplication · Hcltech

CVE-2022-27546

MEDIUM · 6.1 CVSS v3.1 Published 2022-08-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
HCL iNotes is susceptible to a Reflected Cross-site Scripting (XSS) vulnerability caused by improper validation of user-supplied input supplied with a form POST request. A remote attacker could exploit this vulnerability using a specially-crafted URL 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 · moderate confidence

HCL iNotes contains a reflected XSS vulnerability where improper validation of user-supplied input in form POST requests allows attackers to inject malicious scripts. When victims click specially-crafted URLs, the injected scripts execute within the security context of the hosting website, enabling session hijacking via stolen cookie-based authentication credentials.

MitigationImplement proper input validation and output encoding for all user-supplied data in POST requests within iNotes. Deploy the vendor patch when available and validate the fix does not introduce new attack vectors.

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
Hcl InotesApplication
Affected:= 9.0.1= 10.0= 10.0.1= 11.0= 11.0.1= 12.0= 12.0.1
DominoApplication
Affected:= 9.0= 9.0.1= 10.0= 10.0.1= 11.0= 11.0.1= 12.0= 12.0.1

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

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

  1. Identify if HCL Domino or iNotes is installed
    Check for Domino installation directory (Windows: C:\Lotus\Domino or Linux: /opt/ibm/domino), or look for 'IBM\Lotus\Domino' in program files. Also check running services for 'Lotus Domino' or 'IBM Domino'.
    Affected if HCL Domino server software is present on the system
  2. Determine installed Domino version
    Run 'domino -version' from the Domino bin directory, or check the version in the Domino Program directory at '..\ Domino\notes.ini' or via the Domino Administrator client. Alternatively, access the Domino web admin at /webadmin and check server version.
    Affected if Version matches 9.0, 9.0.1, 10.0, 10.0.1, 11.0, 11.0.1, 12.0, or 12.0.1 for Domino; or 9.0.1, 10.0, 10.0.1, 11.0, 11.0.1, 12.0, or 12.0.1 for iNotes
  3. Verify iNotes web access is enabled
    Check the Domino notes.ini configuration file for 'iNotes_WA Enable' or similar iNotes-related settings. Also confirm the iNotes web database (iNotesWA.nsf) exists in the Domino data directory.
    Affected if iNotes web access is enabled and the iNotes database files are present and accessible via HTTP/HTTPS
  4. Confirm iNotes HTTP servlet is accessible
    Test if iNotes responds by accessing a known iNotes URL path such as /iNotes/ or /names.nsf?Login in a web browser. Use curl or a similar tool: curl -I https://yourserver/iNotes/
    Affected if iNotes servlets respond to HTTP requests, indicating the vulnerable POST form handlers are active
  5. Inspect iNotes configuration for input validation settings
    Review the iNotes configuration document in Domino Directory (names.nsf) under Configuration - Servers - All Servers Documents. Check for 'iNotes/DAOS' or custom form settings that may control input validation on POST requests.
    Affected if iNotes is configured with default settings and accepts user-supplied data in form POST requests without explicit input validation rules configured

Your environment is affected if HCL Domino or iNotes is installed with a version matching 9.0.x through 12.0.1 AND the iNotes web interface is enabled and accessible.

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 proper input validation and output encoding for all user-supplied data in POST requests within iNotes. Deploy the vendor patch when available and validate the fix does not introduce new attack vectors.

Fix this in Hcl Inotes Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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