CVE-2025-31970: HCL DFXAnalytics is affected by an Insecure Security Header configuration vulnerability where the Content-Secu

Q: How do I fix CVE-2025-31970?

dfxanalytics: upgrade to 4.1. Exact commands for each OS are on this page.

Q: Is CVE-2025-31970 being exploited?

CVE-2025-31970 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-31970 affect?

CVE-2025-31970 affects dfxanalytics. Severity is medium (CVSS 5.3). 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 vect

Q: How urgent is CVE-2025-31970?

Priority 25/100. Remotely exploitable, no login, no user action

Routine

MEDIUM 5.3REMOTEUPGRADE

CVE-2025-31970 is a medium-severity flaw (CVSS 5.3) affecting dfxanalytics. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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)

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.1% (top 96%)
CISA exploited list	No
Weakness	CWE-358, CWE-79
Published	2026-05-06
Last modified	2026-10-07

Publisher (CNA): HCL Software · Vendor: hcltech

Last updated 2026-10-07 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-05-06 11:16 UTCPublished CVE record published
2026-10-07 09:10 UTCUpdated Record last modified

hcltech dfxanalytics UPGRADE

Affected: < 4.1

Fixed in: 4.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy dfxanalytics || rpm -q dfxanalytics || dfxanalytics --version

2. UPGRADE to 4.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade dfxanalytics

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade dfxanalytics

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-31970?

dfxanalytics: upgrade to 4.1. Exact commands for each OS are on this page.

Is CVE-2025-31970 being exploited?

CVE-2025-31970 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-31970 affect?

CVE-2025-31970 affects dfxanalytics. Severity is medium (CVSS 5.3). 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 vect

How urgent is CVE-2025-31970?

Priority 25/100. Remotely exploitable, no login, no user action

Related CVEs

CVE-2026-56455 MEDIUM 5.3 UPGRADE HCL DFXAnalytics is affected by a Buffer Overflow vulnerability that can lead to a Denial of Service (DoS)
CVE-2026-56456 MEDIUM 5.3 UPGRADE HCL DFXAnalytics is affected by an Internal File Path Disclosure vulnerability
CVE-2026-56454 MEDIUM 5.9 UPGRADE HCL DFXAnalytics is affected by a Deprecated Protocol vulnerability due to the use of TLS 1.0 and TLS 1.1
CVE-2026-56453 MEDIUM 5.5 UPGRADE HCL DFXAnalytics is affected by an Account Takeover via Response Manipulation vulnerability
CVE-2026-35145 LOW 3.1 UPGRADE HCL DFXAnalytics is affected by a Missing HTTP Strict-Transport-Security Header vulnerability

References

← Back to latest CVEs