CVE-2023-45700
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 Launch is vulnerable to HTML injection. This vulnerability may allow a user to embed arbitrary HTML tags in the Web UI potentially leading to sensitive information disclosure.
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 confidenceHCL Launch contains an HTML injection vulnerability in its Web UI that allows users to embed arbitrary HTML tags. This could enable attackers to execute malicious scripts or steal sensitive information through stored XSS attacks.
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>= 7.1.0.0, <= 7.1.2.14>= 7.2.0.0, <= 7.2.3.7>= 7.3.0.0, <= 7.3.2.2CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 Launch installation versionLocate the version information for your HCL Launch installation. This is typically accessible through the Web UI footer, server logs, or installation directories. Check the About section in the Web UI or look for version files in the installation directory.Affected if The installed version falls within any of these ranges: 7.1.0.0 through 7.1.2.14, 7.2.0.0 through 7.2.3.7, or 7.3.0.0 through 7.3.2.2
-
Confirm Web UI is enabledVerify that the HCL Launch Web UI is accessible and in use. Attempt to access the Web UI login page via the standard HTTP/HTTPS port (typically 8080 or 8443). Check server configuration files for Web UI enabled status.Affected if The Web UI is accessible and no external authentication or proxy filtering is blocking direct access to user-supplied input fields in the interface
-
Identify user input points in Web UIReview your HCL Launch Web UI for fields that accept user-supplied text. Common areas include application names, component names, process request descriptions, and resource tags. These are potential injection points.Affected if Users can input custom text directly into Web UI fields without enforced input validation or encoding
You are affected if your HCL Launch version matches any of the three vulnerable ranges AND the Web UI is accessible to users who could inject malicious HTML or script content.
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 vendor-provided patches for HCL Launch. Implement output encoding and input validation on all user-supplied data in the Web UI as a compensating control until the patch is applied.
- 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-45700 — 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-45700 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