Is CVE-2025-54128 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-54128 being exploited in the wild.

How severe is CVE-2025-54128?

Medium severity, with a CVSS score of 4, published 21 July 2025.

Which products and versions are affected?

@haxtheweb/haxcms-nodejs (npm) SEMVER:introduced=0,fixed=11.0.8.

Is there a fix for CVE-2025-54128?

Yes. @haxtheweb/haxcms-nodejs (npm): upgrade to 11.0.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2025-54128 attacked?

It is attacked over the network.

Am I affected by CVE-2025-54128?

Check whether you run @haxtheweb/haxcms-nodejs (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2025-54128: HAX CMS NodeJS disabled Content Security Policy enables XSS

CVE-2025-54128 · Severity: medium · CVSS 4 · Published 2025-07-21

HAX CMS is a microsite management system used to build and maintain web properties. The NodeJS version of HAX CMS has disabled its Content Security Policy (CSP), a critical browser security mechanism that prevents cross-site scripting attacks. If an attacker finds a way to inject malicious code into the application, the lack of CSP would allow arbitrary scripts to run, potentially enabling theft of user session tokens, sensitive data, and account takeover.

Technologies: @haxtheweb/haxcms-nodejs (npm). Vendors: npm.

Quick answers

Is CVE-2025-54128 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-54128 being exploited in the wild.
How severe is CVE-2025-54128?: Medium severity, with a CVSS score of 4, published 21 July 2025.
Which products and versions are affected?: @haxtheweb/haxcms-nodejs (npm) SEMVER:introduced=0,fixed=11.0.8.
Is there a fix for CVE-2025-54128?: Yes. @haxtheweb/haxcms-nodejs (npm): upgrade to 11.0.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2025-54128 attacked?: It is attacked over the network.
Am I affected by CVE-2025-54128?: Check whether you run @haxtheweb/haxcms-nodejs (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

@haxtheweb/haxcms-nodejs (npm): upgrade to 11.0.8 or later
```
npm install @haxtheweb/haxcms-nodejs@11.0.8
```

Technical details

The vulnerability is a missing security control (CWE-79 related) rather than a direct XSS vulnerability. The Helmet middleware's contentSecurityPolicy directive is explicitly disabled in app.js line 52, leaving the application without browser-level XSS protection. Attack vector is network-based and requires user interaction (victim must visit a malicious page or click a link). An attacker who can inject XSS payloads through any means (stored or reflected XSS, CSRF, etc.) can execute arbitrary JavaScript in the user's browser context, exfiltrate session tokens and sensitive local data, and perform actions on behalf of the user. The fix was available in version 11.0.8, which re-enables CSP in the Helmet configuration.

Affected products

HAX HAX CMS NodeJS <=11.0.7

Identifiers

CVE-2025-54128
GHSA-59g8-h59f-8hjp

Timeline

2025-07-21: disclosed: GHSA-59g8-h59f-8hjp published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.