CVE Details
Basic Information
| Title | HAXcms’s Insecure Default Configuration Leads to Unauthenticated Access |
|---|---|
| Type | cve |
| Published | 2025-07-21T20:36:43.580Z |
| Modified | 2025-07-21T21:24:10.832Z |
Product Information
| Vendor | haxtheweb |
|---|---|
| Product | issues |
| Version | < 11.0.7 |
CVSS Information
| Base Score | 9.3 (CRITICAL) |
|---|---|
| Attack Vector | 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 |
Affected Products
- haxtheweb issues < 11.0.7
Additional Information
| CWE List | CWE-1188 |
|---|---|
| Source | GitHub_M |
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.