CVE-2023-28013
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 Verse is susceptible to a Reflected Cross Site Scripting (XSS) vulnerability. By tricking a user into entering crafted markup a remote, unauthenticated attacker could execute script in a victim's web browser to perform operations as the victim and/or steal the victim's cookies, session tokens, or other sensitive information.
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 Verse contains a reflected XSS vulnerability where malicious markup can be injected and reflected back to the user, executing in the victim's browser context. An unauthenticated attacker can trick users into accessing crafted links or content to steal session tokens, cookies, or perform actions as the victim.
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< 3.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 HCL Verse installationLocate the HCL Verse installation and determine the installed version number. This may be found in the application about page, installation directory metadata, or product documentation.Affected if The installed version is below 3.1 (for example, 3.0.x or earlier releases).
-
Confirm web interface accessibilityVerify that the HCL Verse web interface is accessible and operational. This is typically accessible via browser to the server where Verse is hosted.Affected if The web interface is reachable and accepts user input through URL parameters or form fields.
-
Assess user input handlingTest whether user-supplied input in URLs or forms is reflected back in the response without proper encoding. This can be done by submitting simple HTML-safe characters (like <script>alert(1)</script>) in common input fields and observing if they are rendered as-is in the response.Affected if User input is reflected in the response page without sanitization or encoding, allowing injected markup to execute in the browser.
The environment is affected if HCL Verse version is below 3.1 and user input is reflected in web responses without proper encoding.
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 · scoped3.1
Implement proper input validation and output encoding/sanitization for all user-supplied content before rendering in the browser. Consider implementing Content Security Policy headers as an additional defense layer.
Verse 3.1
- 1. Identify the current HCL Verse installation and verify the installed version is below 3.1
- 2. Review the HCL Verse 3.1 release notes on support.hcltechsw.com for upgrade requirements and any prerequisites
- 3. Back up the existing HCL Verse installation and all relevant data
- 4. Follow HCL's official upgrade documentation to update Verse to version 3.1 or later
- 5. After upgrade, verify the new version is 3.1 or higher
- 6. Test that the XSS vulnerability is no longer reproducible
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-28013 — 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-28013 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