CVE-2025-54127: NodeJS version of HAX CMS Has Insecure Default Configuration That Leads to Unauthenticated Access
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.
Published Jul 21, 2025
Affected packages
@haxtheweb/haxcms-nodejs
- Ecosystem
- npm
- Affected
- <= 11.0.6
- Fixed in
- 11.0.7
- Check
npm ls @haxtheweb/haxcms-nodejs
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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, ‘HAXCMS_DISABLE_JWT_CHECKS‘ would be set to ‘true‘ and their deployment would lack session authentication.
insecure-default-configuration-code
Affected Resources
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.
Credited to asareynolds.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology