dbcve.org
DfxanalyticsApplication · Hcltech

CVE-2025-31970

MEDIUM · 6.1 CVSS v3.1 Published 2026-05-06
Fix available
A fix is available. Upgrade to 4.1 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 DFXAnalytics is affected by an Insecure Security Header configuration vulnerability where the Content-Security-Policy does not define strict directives for object-src and base-uri, which could allow an attacker to exploit injection vectors such as Cross-Site Scripting (XSS)

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 · high confidence

HCL DFXAnalytics has a misconfigured Content-Security-Policy header that lacks strict directives for object-src and base-uri. This CSP weakness could allow attackers to exploit injection vectors like Cross-Site Scripting (XSS) by bypassing the intended security restrictions.

MitigationConfigure the Content-Security-Policy header with strict object-src (preferably 'none' or specific allowed sources) and base-uri directives to prevent XSS and injection 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
DfxanalyticsApplication
Affected:< 4.1

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. Determine the installed version of HCL DFXAnalytics
    Locate the version information for your HCL DFXAnalytics installation using the product's built-in about page, version file, or administrative console
    Affected if The installed version is any version prior to 4.1 (for example, 4.0.x, 3.x, or earlier releases)
  2. Capture the Content-Security-Policy header from application responses
    Use a browser developer tool, curl -I, or a proxy to inspect the HTTP response headers returned by your DFXAnalytics server
    Affected if No Content-Security-Policy header is present in the HTTP responses
  3. Verify the object-src directive in the CSP header
    Examine the CSP header value and locate the object-src directive (or lack thereof)
    Affected if The object-src directive is missing, not set to 'none', or allows unrestricted sources (such as '*' or unsafe-inline)
  4. Verify the base-uri directive in the CSP header
    Examine the CSP header value and locate the base-uri directive (or lack thereof)
    Affected if The base-uri directive is missing or allows unrestricted sources (such as '*' or multiple domains not explicitly controlled)
  5. Confirm the CSP is applied to sensitive endpoints
    Verify that the CSP header is present on pages that handle user input, authentication, or display dynamic content
    Affected if The CSP header is only present on static pages but missing from interactive or data-handling endpoints

You are affected if your HCL DFXAnalytics version is below 4.1 AND the Content-Security-Policy header is missing, or missing strict object-src and base-uri directives that would prevent XSS injection attacks.

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

Configure the Content-Security-Policy header with strict object-src (preferably 'none' or specific allowed sources) and base-uri directives to prevent XSS and injection attacks.

Recommended fix Moderate confidence

4.1

  1. Obtain HCL DFXAnalytics version 4.1 or later from the official HCL software distribution channel (support.hcl-software.com or authorized partner)
  2. Review the upgrade documentation provided with version 4.1 for any specific migration requirements
  3. Perform a backup of the existing DFXAnalytics configuration and data
  4. Install version 4.1 or later following the standard HCL product upgrade procedure
  5. Verify that the Content-Security-Policy header now includes strict object-src ('none' or trusted sources only) and base-uri directives
  6. Test the deployment to confirm normal functionality after upgrade

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

Fix this in Dfxanalytics Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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