CVE-2022-44759
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 · uneditedImproper sanitization of SVG files in HCL Leap allows client-side script injection in deployed applications.
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 Leap fails to properly sanitize SVG file uploads, allowing attackers to embed malicious client-side scripts (JavaScript) within SVG content. When users view or interact with deployed applications that render these SVG files, the injected scripts execute in the context of the victim's browser, enabling session hijacking, data theft, or actions on behalf of the user.
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>= 9.0, < 9.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
- 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 installed HCL Leap versionAccess the HCL Leap administration console or check the installation directory for version information. The exact method depends on your deployment but typically involves logging into the admin panel or running a version command.Affected if The installed version is 9.0 or higher but lower than 9.3.1
-
Determine if SVG file uploads are permittedReview the application configuration or form settings that handle file attachments. Check whether any deployed applications accept SVG file uploads as part of forms or user submissions.Affected if SVG file uploads are enabled and users can attach SVG files to forms or applications
-
Check if deployed applications render SVG contentInspect any applications that display uploaded files to users. Look for file viewers, image display components, or attachments sections that could render SVG files in the browser.Affected if Deployed applications display or render uploaded SVG files to end users in the browser context
-
Review content security policy configurationCheck the server or application configuration for Content-Security-Policy headers, specifically whether script-src restrictions would block JavaScript execution from SVG resources.Affected if No CSP is configured or the policy allows script execution from external or inline SVG sources
You are affected if HCL Leap version 9.0 through 9.3.0 is running AND users can upload AND view SVG files that get rendered in the browser.
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 · scoped9.3.1
Implement server-side sanitization of uploaded SVG files to strip or neutralize embedded scripts, or configure content security policy to prevent script execution from SVG resources.
9.3.1 or later
- Upgrade HCL Leap from any version >= 9.0 to version 9.3.1 or later
- Verify the upgrade in a non-production environment first
- Deploy the upgraded version to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.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 $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-44759 — 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-2022-44759 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