dbcve.org
UnicaApplication · Hcltech

CVE-2025-31969

MEDIUM · 6.1 CVSS v3.1 Published 2025-10-12
Fix available
A fix is available. Upgrade to after 25.1.0 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
HCL Unica Platform is impacted by misconfigured Content Security Policy (CSP). These can result in malicious resources getting loaded and browsers may come across certain types of attacks, such as cross-site scripting and clickjacking.

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 Unica Platform contains misconfigured Content Security Policy (CSP) HTTP headers. CSP is designed to prevent XSS and clickjacking by controlling which resources a browser can load. When improperly configured, attackers can inject malicious scripts or trick users into performing unintended actions.

MitigationReview and properly configure CSP headers in the web server or application configuration to whitelist only trusted content sources and restrict inline scripts.

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
UnicaApplication
Affected:<= 25.1.0

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. Confirm HCL Unica Platform is running
    Access the web application URL in a browser or use a command-line tool like curl to make an HTTP request to the server (e.g., curl -I https://<unica-host>:<port>) and observe the response headers
    Affected if The server responds with HTTP headers indicating HCL Unica is running and the response includes CSP headers
  2. Identify the installed version
    Check the product version through the Unica admin console, the WAR file manifest, or the installation directory (look for version.info or similar files in the Unica installation path)
    Affected if The installed version is 25.1.0 or any earlier version within the <=25.1.0 range
  3. Inspect CSP HTTP headers
    Capture HTTP response headers from the Unica web application (using browser DevTools Network tab, curl -I, or a proxy) and locate Content-Security-Policy or Content-Security-Policy-Report-Only headers
    Affected if CSP headers are present and contain any of the following weak directives: unsafe-inline, unsafe-eval, or wildcard (*) sources for script-src, style-src, or object-src
  4. Check for missing or weak CSP directives
    Examine the full CSP header value and verify whether essential directives (default-src, script-src, style-src, img-src, connect-src) are missing or set to overly permissive values like 'self' with unsafe-inline/eval, or have no restrictions on external sources
    Affected if The CSP is absent entirely, or allows unrestricted inline scripts (unsafe-inline), or permits loading resources from any source (*)

The environment is affected if HCL Unica Platform version 25.1.0 or lower is running AND the HTTP responses either lack CSP headers or contain misconfigured CSP headers that allow unsafe-inline, unsafe-eval, or wildcard source restrictions.

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 a release after 25.1.0
Interim mitigation

Review and properly configure CSP headers in the web server or application configuration to whitelist only trusted content sources and restrict inline scripts.

Recommended fix Moderate confidence

HCL Unica Platform 25.1.1 or later (verify exact fixed version on HCL support portal)

  1. Check HCL Unica Platform product documentation or support.hcl-software.com for the specific patch or hotfix addressing CSP configuration
  2. Locate the web server or application server configuration where CSP headers are defined for Unica
  3. Review and properly configure Content-Security-Policy headers to be more restrictive, removing overly permissive directives like 'unsafe-inline' or 'unsafe-eval' if present
  4. Ensure CSP policies explicitly whitelist only trusted content sources and domains
  5. Test the CSP configuration in a non-production environment to verify legitimate functionality is not broken
  6. Deploy the updated configuration or upgrade to the fixed version once available
Caveat Review CSP changes in test environment before production deployment to ensure no legitimate functionality is blocked

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

Fix this in Unica Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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