CVE-2025-54127: haxtheweb issues · Insecure Default Initialization of Resource
Affects haxtheweb issuesSource CVE Database V5
Not known to be exploited · CVSS 9.3 Critical : upgrade to 11.0.7 as a priority.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 11.0.7
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/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 26 Oct 2026.
What to do
Upgrade haxtheweb issues to 11.0.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| haxtheweb issues | Affected
| Fixed in
|
AI-suggested
European organizations should immediately verify their HAXcms version and configuration. The primary mitigation is to upgrade to version 11.0.7 or later, where the default configuration enforces JWT authentication. If upgrading is not immediately feasible, organizations must manually ensure that 'HAXCMS_DISABLE_JWT_CHECKS' is set to 'false' or removed entirely to enable authentication checks. Additionally, restrict network access to the HAXcms backend using firewalls or VPNs to limit exposure. Implement monitoring and logging to detect unauthorized access attempts. Conduct a thorough audit of existing deployments to identify any unauthorized changes or access. Employ web application firewalls (WAFs) with rules tailored to detect anomalous requests targeting HAXcms endpoints. Finally, educate administrators and developers about the risks of deploying development configurations in production environments to prevent similar issues.
Description
HAXcms with nodejs backend allows users to start the server in any HAXsite or HAXcms instance. In versions 11.0.6 and below, the NodeJS version of HAXcms uses an insecure default configuration designed for local development. The default configuration does not perform authorization or authentication checks. If a user were to deploy haxcms-nodejs without modifying the default settings, ‘HAXCMS_DISABLE_JWT_CHECKS‘ would be set to ‘true‘ and their deployment would lack session authentication. This is fixed in version 11.0.7.