HAXcms's Insecure Default Configuration Leads to Unauthenticated Access
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| haxtheweb | issues | affected |
|
No data.
| Vendor | Product | Versions |
|---|---|---|
| Haxtheweb | Haxcms-nodejs | — |
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2025-22261 | NodeJS version of HAX CMS Has Insecure Default Configuration That Leads to Unauthenticated Access |
Github GHSA |
GHSA-f38f-jvqj-mfg6 | NodeJS version of HAX CMS Has Insecure Default Configuration That Leads to Unauthenticated Access |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.456% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Psu
Psu haxcms-nodejs |
|
| CPEs | cpe:2.3:a:psu:haxcms-nodejs:*:*:*:*:*:node.js:*:* | |
| Vendors & Products |
Psu
Psu haxcms-nodejs |
|
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Haxtheweb
Haxtheweb haxcms-nodejs |
|
| Vendors & Products |
Haxtheweb
Haxtheweb haxcms-nodejs |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| 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 HAX CMS 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. | 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. |
| Title | HAX CMS PHP's Insecure Default Configuration Leads to Unauthenticated Access | HAXcms's Insecure Default Configuration Leads to Unauthenticated Access |
| Type | Values Removed | Values Added |
|---|---|---|
| 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 HAX CMS 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. | |
| Title | HAX CMS PHP's Insecure Default Configuration Leads to Unauthenticated Access | |
| Weaknesses | CWE-1188 | |
| References |
| |
| Metrics |
cvssV4_0
|