Security Digest · Vulnerability record
CVE-2025-54127: NodeJS version of HAX CMS Has Insecure Default Configuration That Leads to Unauthenticated Access
HAXcms with nodejs backend allows users to start the server in any HAXsite or HAXcms instance.
CVSS 9.3 Critical EPSS 0.4% · p37
Should you act?
Critical and remotely reachable
No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.
- Not in CISA KEV, but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
- EPSS 0.4%, percentile 37: FIRST’s model estimates a 0.4% chance of exploitation activity in the next 30 days, higher than 37% of all scored CVEs (low). EPSS is a probability, not a verdict.
- Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
- Only applies if your dependency tree includes
@haxtheweb/haxcms-nodejs(npm) <= 11.0.6, fixed in 11.0.7. Check your lockfile, including transitive dependencies.
What it is
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, ‘HAXCMSDISABLEJWTCHECKS‘ would be set to ‘true‘ and their deployment would lack session authentication. This is fixed in version 11.0.7.
From the GitHub advisory
Summary The NodeJS version of HAX CMS uses an insecure default configuration designed for local development. The default configuration does not perform authorization or authentication checks.
Details If a user were to deploy haxcms-nodejs without modifying the default settings, ‘HAXCMSDISABLEJWTCHECKS‘ would be set to ‘true‘ and their deployment would lack session authentication.
Affected Resources - package.json:13
PoC To reproduce this vulnerability, install HAX CMS NodeJS. The application will load without JWT checks enabled.
Impact Without security checks in place, an unauthenticated remote attacker could access, modify, and delete all site information.
Weakness type: CWE-1188.
Product: @haxtheweb/haxcms-nodejs (npm) · Assigned by: GitHub_M · Published: 2025-07-21
Affected and fixed versions
| Ecosystem | Package | Vulnerable | First fixed |
|---|---|---|---|
| npm | @haxtheweb/haxcms-nodejs | <= 11.0.6 | 11.0.7 |
| Vendor | Product | Affected versions (per CVE record) |
|---|---|---|
| haxtheweb | issues | < 11.0.7 |
Severity scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| GitHub_M | 4.0 | 9.3 Critical | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N |
| GitHub | 4.0 | 9.3 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N |
- Attack vector: network (remotely reachable)
- Attack complexity: low
- Attack requirements: none
- Privileges required: none (no login)
- User interaction: none
CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.
Exploitation and urgency
- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation poc, automatable no, technical impact partial.
- FIRST EPSS (model of 2026-10-21): 0.44% probability of exploitation activity in the next 30 days; percentile 37.
Timeline
- — CVE record published by GitHub_M
- — GitHub-reviewed advisory GHSA-f38f-jvqj-mfg6 published (critical)
- — CVE record last updated
Sources and references
Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.
Vulnerability records
- GitHub Advisory GHSA-f38f-jvqj-mfg6 github.com
- CVE.org record CVE-2025-54127 cve.org
- NVD entry CVE-2025-54127 nvd.nist.gov
Other references from the CVE record and advisory
- github.com github.com