CVE-2025-54127
BaseFortify
Publication date: 2025-07-21
Last updated on: 2025-07-30
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| psu | haxcms-nodejs | to 11.0.7 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-1188 | The product initializes or sets a resource with a default that is intended to be changed by the product's installer, administrator, or maintainer, but the default is not secure. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in HAXcms with a NodeJS backend in versions 11.0.6 and below. The default configuration is insecure and intended for local development only. It disables authorization and authentication checks by setting 'HAXCMS_DISABLE_JWT_CHECKS' to 'true', which means if deployed without changing these defaults, the server will lack session authentication, allowing unauthorized users to start the server and potentially access or control the HAXsite or HAXcms instance.
How can this vulnerability impact me? :
If you deploy HAXcms NodeJS backend without modifying the default insecure configuration, attackers can start the server without authentication or authorization. This can lead to unauthorized access, control over the CMS instance, potential data exposure, and manipulation of content or server behavior, posing a high security risk.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
You can detect this vulnerability by checking if the HAXcms NodeJS server is running with the default insecure configuration where 'HAXCMS_DISABLE_JWT_CHECKS' is set to 'true'. This indicates that session authentication is disabled. On the system running HAXcms, you can check environment variables or configuration files for this setting. For example, use the command 'printenv | grep HAXCMS_DISABLE_JWT_CHECKS' on the server to see if this variable is set to true. Additionally, scanning for open ports where the HAXcms NodeJS server is listening and testing if authentication is required can help detect the vulnerability.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability immediately, upgrade HAXcms NodeJS to version 11.0.7 or later where the issue is fixed. If upgrading is not immediately possible, ensure that the environment variable 'HAXCMS_DISABLE_JWT_CHECKS' is set to 'false' or removed to enable session authentication. Also, avoid deploying the server with the default development configuration in production environments. Implement proper authorization and authentication checks to prevent unauthorized access.