# CVE-2025-54127: HAX CMS NodeJS insecure default configuration

Source: https://junglewise.ai/threats/cve-2025-54127-hax-cms-nodejs-insecure-default-configuration  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2025-07-21. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

CVE-2025-54127 · Severity: medium · CVSS 4 · Published 2025-07-21

HAX CMS is a NodeJS-based content management system used to build and publish websites. The application ships with an insecure default configuration that disables authentication checks (JWT verification), allowing any unauthenticated attacker on the network to read, modify, or delete all website content and data without credentials.

Technologies: [@haxtheweb/haxcms-nodejs (npm)](https://junglewise.ai/threats/technologies/haxtheweb-haxcms-nodejs). Vendors: [npm](https://junglewise.ai/threats/vendors/npm).

## Quick answers

**Is CVE-2025-54127 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2025-54127 being exploited in the wild.

**How severe is CVE-2025-54127?** Medium severity, with a CVSS score of 4, published 21 July 2025.

**Which products and versions are affected?** @haxtheweb/haxcms-nodejs (npm) SEMVER:introduced=0,fixed=11.0.7.

**Is there a fix for CVE-2025-54127?** Yes. @haxtheweb/haxcms-nodejs (npm): upgrade to 11.0.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2025-54127 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2025-54127?** Check whether you run @haxtheweb/haxcms-nodejs (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- @haxtheweb/haxcms-nodejs (npm): upgrade to 11.0.7 or later

  ```sh
  npm install @haxtheweb/haxcms-nodejs@11.0.7
  ```


## Technical details

The vulnerability is a configuration management flaw (CWE-1188: Insecure Default Initialization with Hard-Coded Network Resource Configuration Data) in which the NodeJS version of HAX CMS defaults to setting 'HAXCMS_DISABLE_JWT_CHECKS' to 'true', disabling session authentication entirely. This insecure default is intended for local development but is exposed if deployed to production without modification. The vulnerability is remotely exploitable over the network with no authentication, privileges, or user interaction required (CVSS vector: AV:N/AC:L/AT:N/PR:N/UI:N). An unauthenticated attacker can access, modify, or delete all site information via API calls. The vulnerability is patched in version 11.0.7; affected versions are up to and including 11.0.6.

## Affected products

- HAX haxcms-nodejs <=11.0.6

## Identifiers

- CVE-2025-54127
- GHSA-f38f-jvqj-mfg6

## Timeline

- 2025-07-21: disclosed
- 2025-07-21: patched: Version 11.0.7 patches the vulnerability

## References

- [https://github.com/haxtheweb/issues/security/advisories/GHSA-f38f-jvqj-mfg6](https://github.com/haxtheweb/issues/security/advisories/GHSA-f38f-jvqj-mfg6)

## Related threats

- [haxtheweb HAX CMS denial of service in createSite endpoint](https://junglewise.ai/threats/cve-2026-46357-haxtheweb-hax-cms-denial-of-service-in-createsite-endpoint)
- [HAX CMS account takeover via Stored XSS and token exposure](https://junglewise.ai/threats/cve-2026-46511-hax-cms-account-takeover-via-stored-xss-and-token-exposure)
- [haxtheweb HAX CMS stored XSS in video-player component](https://junglewise.ai/threats/cve-2026-46496-haxtheweb-hax-cms-stored-xss-in-video-player-component)
- [HAX CMS stored XSS in iframe elements](https://junglewise.ai/threats/cve-2026-46396-hax-cms-stored-xss-in-iframe-elements)
- [HAX CMS private key disclosure and JWT forgery in Node.js backend](https://junglewise.ai/threats/cve-2026-46395-hax-cms-private-key-disclosure-and-jwt-forgery-in-node-js-backend)