CVE-2025-54127: HAXcms's Insecure Default Configuration Leads to Unauthenticated Access
haxtheweb · issues
Affected: haxtheweb issues · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 40% of scored CVEs
DescriptionCVE.org
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.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- haxtheweb · issues< 11.0.7
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Weakness
- Initialization of a Resource with an Insecure Default · Misconfiguration and Insecure Design
- Vendor
- haxtheweb
- Published
- July 2025
CoverageNo articles yet
No CyberSIXT article names CVE-2025-54127 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.