Quick answers
- Is CVE-2025-54137 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-54137 being exploited in the wild.
- How severe is CVE-2025-54137?
- Low severity, with a CVSS score of 3.1, published 21 July 2025.
- Which products and versions are affected?
- @haxtheweb/haxcms-nodejs (npm) SEMVER:introduced=0,fixed=11.0.10.
- Is there a fix for CVE-2025-54137?
- Yes. @haxtheweb/haxcms-nodejs (npm): upgrade to 11.0.10 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-54137 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2025-54137?
- 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.10 or later
npm install @haxtheweb/haxcms-nodejs@11.0.10
Technical details
This vulnerability stems from the use of default, hardcoded credentials and cryptographic keys in the HAX CMS NodeJS implementation (CWE-1392, CWE-1393, CWE-1394). The HAXCMS.js and HAXCMSClass components contain fixed credentials for user and superuser accounts, as well as default JWT private keys. The attack vector is network-based with no authentication required and no user interaction needed. An unauthenticated remote attacker can obtain these secrets from the public haxtheweb GitHub repositories and use them to authenticate to unconfigured self-hosted instances without modification of default secrets. The attacker can then modify website content, access sensitive information, and potentially escalate attacks. The vulnerability was patched in version 11.0.10; versions 11.0.0 and earlier are affected.
Affected products
- haxtheweb @haxtheweb/haxcms-nodejs <=11.0.0
Identifiers
- CVE-2025-54137
- GHSA-5fpv-5qvh-7cf3
Timeline
- 2025-07-21: disclosed: Advisory published
- 2025-07-21: patched: Version 11.0.10 available
- 2025-07-22: kev added: CVE-2025-54137 published by NVD