CVE-2025-54128: haxtheweb issues · Cross-site Scripting
Affects haxtheweb issuesSource CVE Database V5
Not known to be exploited · CVSS 7.2 High : upgrade to 11.0.8 soon.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 11.0.8
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:H/SC:L/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 21 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Upgrade haxtheweb/issues to 11.0.8.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
npmhaxtheweb/issuespkg:npm/haxtheweb/issuesOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
European organizations should immediately upgrade HAX CMS to version 11.0.8 or later, where the CSP is properly enabled and configured. In addition to upgrading, organizations should: 1) Review and enforce strict Content Security Policies tailored to their microsite content to restrict script sources and prevent inline script execution. 2) Conduct thorough input validation and output encoding to prevent injection of malicious scripts, even with CSP in place. 3) Use security headers beyond CSP, such as X-Content-Type-Options, X-Frame-Options, and Strict-Transport-Security, to harden the web application. 4) Perform security audits and penetration testing focusing on XSS vectors to identify any residual vulnerabilities. 5) Educate users and administrators about phishing risks and safe browsing practices to mitigate social engineering exploitation. 6) Monitor web traffic and logs for suspicious activities indicative of attempted XSS exploitation. 7) If immediate upgrade is not feasible, consider implementing a reverse proxy or Web Application Firewall (WAF) with rules to detect and block XSS payloads targeting the affected endpoints. These steps go beyond generic advice by emphasizing CSP configuration, layered defenses, and user awareness specific to the HAX CMS environment.
Description
HAX CMS NodeJs allows users to manage their microsite universe with a NodeJs backend. In versions 11.0.7 and below, 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. The contentSecurityPolicy value is explicitly disabled in the application's Helmet configuration in app.js. This is fixed in version 11.0.8.