Metrics
Affected Vendors & Products
| 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 |
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Wed, 30 Jul 2025 17:15:00 +0000
| 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
|
Wed, 23 Jul 2025 20:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Haxtheweb
Haxtheweb haxcms-nodejs |
|
| Vendors & Products |
Haxtheweb
Haxtheweb haxcms-nodejs |
Tue, 22 Jul 2025 20:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Mon, 21 Jul 2025 21:30:00 +0000
| 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 |
Mon, 21 Jul 2025 20:45:00 +0000
| 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
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2025-07-22T19:56:43.124Z
Reserved: 2025-07-16T23:53:40.509Z
Link: CVE-2025-54127
Updated: 2025-07-22T19:56:38.713Z
Status : Analyzed
Published: 2025-07-21T21:15:26.403
Modified: 2025-07-30T17:03:34.940
Link: CVE-2025-54127
No data.
OpenCVE Enrichment
Updated: 2025-07-23T20:19:26Z
EUVD
Github GHSA