dbcve.org
Domino LeapApplication · Hcltech

CVE-2024-30115

MEDIUM · 5.4 CVSS v3.1 Published 2025-04-30
Fix available
A fix is available. Upgrade to 1.1.4 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 · moderate confidence

This is a stored cross-site scripting (XSS) vulnerability in HCL Leap's HTML widget where insufficient input sanitization allows authenticated attackers to inject malicious client-side scripts (JavaScript) that execute in the browsers of users viewing the deployed application.

MitigationRestrict or disable the HTML widget in untrusted applications, implement strict Content Security Policy (CSP) headers, and validate/sanitize all user-supplied HTML content before rendering.

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
Domino LeapApplication
Affected:>= 1.1, < 1.1.4

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 HCL Leap installation and version
    Locate the HCL Leap (Domino Leap) installation directory and check the version manifest or about page. Common paths include the Domino data directory or the Leap installation folder. Look for version files like 'leap-version.properties' or check the application's About/Version information in the HCL Leap interface.
    Affected if Installed version is 1.1.x and less than 1.1.4 (i.e., 1.1.0 through 1.1.3)
  2. Verify HTML widget is in use
    Review deployed HCL Leap applications (forms) to identify whether the HTML widget component is present. Access the Leap application designer and examine forms for HTML widget instances, or query the application metadata/database for 'HTML' widget references.
    Affected if Any production application uses the HTML widget to render user-supplied or dynamic HTML content
  3. Inspect HTML widget content sources
    Examine the HTML widget configuration in affected applications to determine whether the HTML content source is set to accept user input, external data, or unsanitized values. Check the widget properties panel in the Leap application designer.
    Affected if HTML widget source is connected to user-provided fields, formula evaluations, or external data sources without sanitization
  4. Review deployed application accessibility
    Determine whether the applications containing HTML widgets are accessible to authenticated users beyond the application administrators. Check application security settings and user roles in the Leap administration console.
    Affected if Non-administrator authenticated users can access applications with HTML widgets

Environment is affected if running Domino Leap version 1.1.0 through 1.1.3 AND any application uses the HTML widget with content that could be influenced by authenticated users.

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 1.1.4 or later
Fixed in 1.1.4
Interim mitigation

Restrict or disable the HTML widget in untrusted applications, implement strict Content Security Policy (CSP) headers, and validate/sanitize all user-supplied HTML content before rendering.

Recommended fix High confidence

HCL Domino Leap 1.1.4

  1. Back up the current HCL Domino Leap installation and all custom applications
  2. Download HCL Domino Leap version 1.1.4 from the official HCL support portal (support.hcl-software.com)
  3. Follow HCL's official upgrade documentation to install version 1.1.4
  4. After upgrade, verify the version is correctly displayed as 1.1.4 in the Domino Leap administration interface
  5. Test applications that use the HTML widget to confirm the XSS vulnerability is remediated
Caveat No specific breaking changes documented for this minor version upgrade

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

Fix this in Domino Leap Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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