dbcve.org
Domino LeapApplication · Hcltech

CVE-2024-30145

MEDIUM · 6.1 CVSS v3.1 Published 2025-04-30
Fix available
A fix is available. Upgrade to 1.1.5 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Multiple vectors in HCL Domino Volt and Domino Leap allow client-side script injection in the authoring environment and 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 confidence

This is a Cross-Site Scripting (XSS) vulnerability in HCL Domino Volt and Domino Leap low-code application platforms. The flaw allows injection of malicious client-side scripts through multiple vectors in both the application authoring environment and in deployed applications, enabling attackers to execute arbitrary JavaScript in users' browsers.

MitigationImplement input validation and output encoding for all user-supplied data, configure Content Security Policy (CSP) headers to restrict script execution, and apply vendor-supplied patches when released. Review existing applications for XSS vulnerabilities in the interim.

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.5

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

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

  1. Identify HCL Domino Leap installation
    Locate Domino Leap by checking for its service process, installation directory (typically under IBM/Domino or HCL), or by accessing the Domino Leap administration console at /domino-leap/
    Affected if HCL Domino Leap software is present in the environment
  2. Determine installed Domino Leap version
    Access the Domino Leap administration console and navigate to the About page, or check the version metadata in the installation directory. Alternatively, query the server for version information through the Domino Leap admin interface.
    Affected if The installed version is 1.1.0 through 1.1.4 (versions >= 1.1 but < 1.1.5)
  3. Check if application authoring environment is exposed
    Verify network accessibility of the Domino Leap application builder interface (typically at /appBuilder/ or similar endpoints). Review reverse proxy or firewall rules controlling access to authoring URLs.
    Affected if The authoring environment is accessible from untrusted networks without authentication controls
  4. Identify deployed applications handling user input
    Review the Domino Leap application catalog to enumerate deployed applications. For each application, examine form configurations and data entry points that accept user-supplied content.
    Affected if Deployed applications contain form fields, rich text editors, or data capture interfaces that accept and display user input without visible output encoding configuration
  5. Inspect Content Security Policy configuration
    Check the Domino Leap server configuration and deployed application settings for Content-Security-Policy headers. Look for CSP rules in the server's internet site documents or application security settings.
    Affected if CSP headers are not configured or explicitly allow 'unsafe-inline' or 'unsafe-inline' script sources

A user is affected if HCL Domino Leap version 1.1 through 1.1.4 is installed and exposed environments handle user-supplied data without proper CSP controls.

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.5 or later
Fixed in 1.1.5
Interim mitigation

Implement input validation and output encoding for all user-supplied data, configure Content Security Policy (CSP) headers to restrict script execution, and apply vendor-supplied patches when released. Review existing applications for XSS vulnerabilities in the interim.

Recommended fix High confidence

HCL Domino Leap 1.1.5

  1. 1. Back up your current Domino Leap installation and application data
  2. 2. Download HCL Domino Leap version 1.1.5 from the HCL Software support portal (support.hcl-software.com)
  3. 3. Stop the Domino Leap server services
  4. 4. Install Domino Leap 1.1.5 following the standard upgrade procedure
  5. 5. Verify the installation completed successfully
  6. 6. Test that XSS protections are working in both the authoring environment and deployed applications
  7. 7. Restart Domino Leap server services
Caveat No significant breaking changes expected; this is a security patch release

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

Fix this in Domino Leap Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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