dbcve.org
Hcl Devops DeployApplication · Hcltechsw

CVE-2025-0272

HIGH · 7.6 CVSS v3.1 Published 2025-04-03
Fix available
A fix is available. Upgrade to 7.1.2.22 / 7.2.3.15 or later.
See remediation →
80/100
Remediation priority · High
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
HCL DevOps Deploy / HCL 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 · moderate confidence

HCL DevOps Deploy and HCL Launch contain an HTML injection vulnerability in the Web UI. Attackers can embed arbitrary HTML tags through user-controllable input fields, potentially allowing session hijacking, credential theft, or sensitive information disclosure through crafted HTML content.

MitigationImplement proper input validation and output encoding for all user-supplied content rendered in the Web UI. Use context-aware HTML sanitization to strip malicious tags while preserving benign formatting.

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 Devops DeployApplication
Affected:>= 8.0.0.0, < 8.0.1.5>= 8.1.0, < 8.1.0.1
Hcl LaunchApplication
Affected:>= 7.0.0.0, <= 7.0.5.26>= 7.1.0.0, < 7.1.2.22>= 7.2.0.0, < 7.2.3.15>= 7.3.0.0, <= 7.3.2.9

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
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/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 the installed HCL product and version
    Locate the product version through the Web UI About page, installation directory metadata, or version file. For HCL DevOps Deploy, check the installation path for a version file; for HCL Launch, check the installation directory for version information.
    Affected if The installed version falls within any of the affected ranges: HCL DevOps Deploy 8.0.0.0 to before 8.0.1.5 or 8.1.0 to before 8.1.0.1; HCL Launch 7.0.0.0 to 7.0.5.26, 7.1.0.0 to before 7.1.2.22, 7.2.0.0 to before 7.2.3.15, or 7.3.0.0 to 7.3.2.9
  2. Confirm Web UI is accessible
    Verify the HCL DevOps Deploy or HCL Launch web interface is reachable by accessing the application URL (typically port 8443 or 8080). Attempt to log in or access the dashboard.
    Affected if The Web UI is exposed and accessible, enabling the HTML injection attack surface
  3. Identify user-controllable input fields in the Web UI
    Navigate to common input areas such as application names, component names, process properties, or user profile fields. These fields accept user-supplied content that gets rendered in the UI.
    Affected if User-controllable input fields exist and accept HTML content without proper sanitization

You are affected if your installed HCL DevOps Deploy or HCL Launch version falls within the affected ranges AND the Web UI with user input fields is accessible.

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 7.1.2.22 / 7.2.3.15 / 8.0.1.5 or later
Fixed in 7.1.2.227.2.3.158.0.1.5
Interim mitigation

Implement proper input validation and output encoding for all user-supplied content rendered in the Web UI. Use context-aware HTML sanitization to strip malicious tags while preserving benign formatting.

Recommended fix High confidence

HCL DevOps Deploy 8.0.1.5+ or 8.1.0.1+; HCL Launch 7.0.5.27+, 7.1.2.22+, 7.2.3.15+, or 7.3.3.0+

  1. 1. Identify the currently installed HCL DevOps Deploy or HCL Launch version by checking the application server or product documentation.
  2. 2. For HCL DevOps Deploy users: Upgrade to version 8.0.1.5 or later if using the 8.0.x branch.
  3. 3. For HCL DevOps Deploy users: Upgrade to version 8.1.0.1 or later if using the 8.1.x branch.
  4. 4. For HCL Launch users on 7.0.x: Upgrade to version 7.0.5.27 or later (the next patch after 7.0.5.26).
  5. 5. For HCL Launch users on 7.1.x: Upgrade to version 7.1.2.22 or later.
  6. 6. For HCL Launch users on 7.2.x: Upgrade to version 7.2.3.15 or later.
  7. 7. For HCL Launch users on 7.3.x: Upgrade to version 7.3.3.0 or later (the next release after 7.3.2.9).
  8. 8. After upgrading, verify the installation and test the Web UI functionality.
Caveat Review HCL upgrade documentation for your specific version path as minor version upgrades may include configuration changes; test in non-production environment first

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

Fix this in Hcl Devops Deploy Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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