How severe is GHSA-59g8-h59f-8hjp?

No CVSS score has been assigned to GHSA-59g8-h59f-8hjp yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-59g8-h59f-8hjp?

GHSA-59g8-h59f-8hjp affects the following packages: @haxtheweb/haxcms-nodejs (npm). Ecosystems affected: npm.

How do I fix GHSA-59g8-h59f-8hjp?

Update @haxtheweb/haxcms-nodejs to 11.0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-59g8-h59f-8hjp is resolved across your whole dependency graph.

How do I detect GHSA-59g8-h59f-8hjp in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @haxtheweb/haxcms-nodejs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-59g8-h59f-8hjp if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is GHSA-59g8-h59f-8hjp actively exploited in the wild?

No public exploit code has been indexed for GHSA-59g8-h59f-8hjp yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-59g8-h59f-8hjp?

GHSA-59g8-h59f-8hjp has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 14th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-59g8-h59f-8hjp?

GHSA-59g8-h59f-8hjp is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-59g8-h59f-8hjp published, and has it been updated?

GHSA-59g8-h59f-8hjp was published on July 21, 2025 and was last updated on July 21, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

NodeJS version of HAX CMS Has Disabled Content Security Policy That Enables Cross-Site ScriptingGHSA-59g8-h59f-8hjp

Fix: haxtheweb/haxcms-nodejs@ddb9351

GHSA-59g8-h59f-8hjp is a Cross-site Scripting (XSS) vulnerability in @haxtheweb/haxcms-nodejs. A fix is available for @haxtheweb/haxcms-nodejs — see the affected versions and patch details below.

Also known asCVE-2025-54128

Published

Jul 21, 2025

Updated

Jul 21, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for GHSA-59g8-h59f-8hjp.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs14th percentile — riskier than 14% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

1other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@haxtheweb/haxcms-nodejsnpm

2Kdownloads / week

Description

Summary

The NodeJS version of HAX CMS has a disabled Content Security Policy (CSP). This configuration is insecure for a production application because it does not protect against cross-site-scripting attacks.

Details

The contentSecurityPolicy value is explicitly disabled in the application's Helmet configuration in app.js.

permissive-csp-code

Affected Resources

app.js:52

PoC

To reproduce this vulnerability, install HAX CMS NodeJS. The application will load without a CSP configured.

Impact

In conjunction with an XSS vulnerability, an attacker could execute arbitrary scripts and exfiltrate data, including session tokens and sensitive local data.

Additional Information

OWASP: Content Security Policy

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@haxtheweb/haxcms-nodejs`	all versions	11.0.8`npm install @haxtheweb/haxcms-nodejs@11.0.8`

Affected Products

1 product · 1 configurations

Application

haxcms-nodejspsu

< 11.0.8

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @haxtheweb/haxcms-nodejs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @haxtheweb/haxcms-nodejs to 11.0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-59g8-h59f-8hjp is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

### Summary The NodeJS version of HAX CMS has a disabled Content Security Policy (CSP). This configuration is insecure for a production application because it does not protect against cross-site-scripting attacks. ### Details The `contentSecurityPolicy` value is explicitly disabled in the application's Helmet configuration in `app.js`. ![permissive-csp-code](https://github.com/user-attachments/assets/8ec6c63c-9f9f-413e-be7e-ed14913da91c) #### Affected Resources - [app.js:52](https://github.com/haxtheweb/haxcms-nodejs/blob/b1f95880b42fea6ed07855b5804b29b182ec5e07/src/app.js#L52) ### PoC To

O3 Security · Impact-Aware SCA

Is GHSA-59g8-h59f-8hjp in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works