dbcve.org
Hcl LeapApplication · Hcltech

CVE-2024-30113

MEDIUM · 5.4 CVSS v3.1 Published 2025-04-24
Fix available
A fix is available. Upgrade to 9.3.6 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Insufficient sanitization policy in HCL Leap allows client-side script injection in the deployed application through the HTML widget.

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 confidence

HCL Leap contains a cross-site scripting (XSS) vulnerability in its HTML widget due to insufficient input sanitization. Attackers can inject malicious client-side scripts into deployed Leap applications through the HTML widget, potentially executing in users' browsers.

MitigationImplement proper input validation and output encoding/sanitization in the HTML widget to neutralize script injection attempts. Consider using a allowlist approach or established sanitization libraries.

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 LeapApplication
Affected:< 9.3.6

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

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

  1. Identify installed HCL Leap version
    Access HCL Leap administration console or check the installation directory for version metadata. Common paths include the About section in the Leap UI or checking version files in the installation directory.
    Affected if The installed version is lower than 9.3.6 (e.g., 9.3.5, 9.3.0, earlier releases)
  2. Locate applications using HTML widgets
    Review deployed Leap applications in the application management section of the Leap administration console. Identify forms or pages that contain HTML widgets where untrusted user input could be injected.
    Affected if Any deployed application contains HTML widgets that accept or display user-supplied content without sanitization
  3. Inspect HTML widget configuration
    Open each application containing HTML widgets in the Leap designer. Examine the widget properties and any JavaScript or HTML code embedded within the widget configuration.
    Affected if The HTML widget contains raw HTML or JavaScript that processes user input without output encoding or sanitization enabled
  4. Verify input handling in forms
    Test form submissions through the HTML widget by entering test script tags (e.g., <script>alert(1)</script>) in input fields and observing if the script executes upon page reload or display.
    Affected if Injected script tags render as executable code rather than being escaped or neutralized

You are affected if HCL Leap version is below 9.3.6 AND any deployed application uses HTML widgets that handle user input without proper sanitization, allowing script injection to execute in browsers.

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.

dbcve · scoped
Upgrade available Upgrade to 9.3.6 or later
Fixed in 9.3.6
Interim mitigation

Implement proper input validation and output encoding/sanitization in the HTML widget to neutralize script injection attempts. Consider using a allowlist approach or established sanitization libraries.

Recommended fix High confidence

HCL Leap 9.3.6

  1. Obtain HCL Leap 9.3.6 from the HCL support portal at support.hcl-software.com
  2. Review HCL Leap upgrade documentation for your current version
  3. Perform a backup of your current Leap deployment and databases
  4. Execute the upgrade to version 9.3.6 following standard HCL upgrade procedures
  5. Verify the HTML widget now properly sanitizes user input and prevents script injection
  6. Test deployed applications using the HTML widget to confirm the XSS vulnerability is remediated

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Hcl Leap Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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 locally
dbcve dependency scanner

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