CVE-2023-37535
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 · uneditedInsufficient URI protocol whitelist in HCL Domino Volt and Domino Leap allow script injection through query parameters.
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 confidenceHCL Domino Volt and Domino Leap have an insufficient URI protocol whitelist that allows attackers to inject malicious scripts through query parameters. This is a reflected Cross-Site Scripting (XSS) vulnerability where the application fails to properly validate and restrict URI protocols in user-supplied input.
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>= 1.1, < 1.1.3CVSS 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 HCL Domino Leap installationLocate the HCL Domino Leap installation directory and check the product version file, or access the application admin interface to view the version informationAffected if The installed version is HCL Domino Leap >= 1.1 and < 1.1.3
-
Confirm product nameVerify that the affected product is HCL Domino Leap (not Domino Volt, which has the same vulnerability but was not listed with specific version ranges)Affected if The product is HCL Domino Leap within the version range 1.1 to 1.1.2.x
-
Check application accessibilityDetermine if the HCL Domino Leap web interface is accessible to users or attackers via HTTP/HTTPSAffected if The application is network-accessible and accepts user-supplied query parameters in URLs
-
Verify query parameter reflectionTest if the application reflects query parameters back in HTTP responses without proper URI protocol validation (e.g., submit a URL with a javascript: or data: protocol in a query parameter)Affected if Query parameters are reflected in responses without validation and the installed version is in the affected range
A user is affected if HCL Domino Leap version 1.1 through 1.1.2.x is installed and the web interface processes user-supplied query parameters that could contain malicious URI protocols.
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.
dbcve · scoped1.1.3
Implement a strict URI protocol whitelist that only allows safe, expected protocols (e.g., https, mailto) and sanitize or encode all query parameters before reflecting them in responses.
Domino Leap 1.1.3
- 1. Back up your current Domino Leap installation and data
- 2. Download HCL Domino Leap version 1.1.3 from the official HCL support portal (support.hcl-software.com)
- 3. Review HCL's upgrade documentation for Domino Leap 1.1.3
- 4. Install the upgrade following HCL's standard upgrade procedure
- 5. Verify the installation and test that applications function correctly
- 6. Confirm the XSS vulnerability is resolved by testing with the previously vulnerable query parameters
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37535 — 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-2023-37535 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