CVE-2025-59849
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 management of Content Security Policy in HCL BigFix Remote Control Lite Web Portal (versions 10.1.0.0326 and lower) may allow the execution of malicious code in web pages.
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 BigFix Remote Control Lite Web Portal versions 10.1.0.0326 and below has improper Content Security Policy management, allowing malicious code execution in web pages. This CSP misconfiguration permits scripts to execute from unauthorized sources, potentially enabling XSS attacks.
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>= 8.0.0.0, < 8.0.1.11>= 8.1.0, < 8.1.2.4>= 7.3.0.0, < 7.3.2.16CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed HCL productCheck if HCL DevOps Deploy or HCL Launch is installed by looking for their installation directories, services, or process executables. Common paths: /opt/HCL/ for Linux, C:\Program Files\HCL\ for WindowsAffected if Either HCL DevOps Deploy or HCL Launch is installed
-
Determine installed version of HCL DevOps DeployRun the product's version command or check version files in the installation directory. For DevOps Deploy, check the version info in the UI or version.properties file in the installation directoryAffected if Version is >= 8.0.0.0 and < 8.0.1.11, or >= 8.1.0 and < 8.1.2.4
-
Determine installed version of HCL LaunchRun the product's version command or check version files in the installation directory. For HCL Launch, check the version info in the UI or version.info file in the installation directoryAffected if Version is >= 7.3.0.0 and < 7.3.2.16
-
Inspect CSP headers on web portalAccess the web portal login page and use browser dev tools or a tool like curl to view HTTP response headers. Look for Content-Security-Policy header and examine script-src directivesAffected if CSP header allows scripts from untrusted sources or uses unsafe-inline/unsafe-eval in script-src directive
-
Check if web portal is exposedVerify if the web interface is accessible over HTTP/HTTPS. Check network configuration and listening ports (typically 8443, 8080, or 9443 for HCL products)Affected if Web portal is externally accessible and CSP is misconfigured
You are affected if you have HCL DevOps Deploy (versions 8.0.0.0-8.0.1.11 or 8.1.0-8.1.2.4) or HCL Launch (versions 7.3.0.0-7.3.2.16) installed with their web portals having improper CSP configuration.
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 · scoped7.3.2.168.0.1.118.1.2.4
Upgrade to a version higher than 10.1.0.0326 once available, or implement proper CSP headers restricting script sources to trusted domains only.
HCL DevOps Deploy 8.0.1.11 or 8.1.2.4; HCL Launch 7.3.2.16
- Upgrade HCL DevOps Deploy to version 8.0.1.11 if using 8.0.0.x, or to version 8.1.2.4 if using 8.1.x
- Upgrade HCL Launch to version 7.3.2.16
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-59849 — 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-2025-59849 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