CVE-2025-54137 Vulnerability Analysis & Exploit Details

CVE-2025-54137
Vulnerability Scoring

7.3
/10
Very High Risk

Highly exploitable, CVE-2025-54137 poses a critical security risk that could lead to severe breaches.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2025-54137 Details

Status: Analyzed

Last updated: 🕒 22 Aug 2025, 15:20 UTC
Originally published on: 🕙 22 Jul 2025, 22:15 UTC

Time between publication and last update: 30 days

CVSS Release: version 3

CVSS3 Source

security-advisories@github.com

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

CVE-2025-54137 Vulnerability Summary

CVE-2025-54137: HAX CMS NodeJS allows users to manage their microsite universe with a NodeJS backend. Versions 11.0.9 and below were distributed with hardcoded default credentials for the user and superuser accounts. Additionally, the application has default private keys for JWTs. Users aren't prompted to change credentials or secrets during installation, and there is no way to change them through the UI. An unauthenticated attacker can read the default user credentials and JWT private keys from the public haxtheweb GitHub repositories. These credentials and keys can be used to access unconfigured self-hosted instances of the application, modify sites, and perform further attacks. This is fixed in version 11.0.10.

Assessing the Risk of CVE-2025-54137

Access Complexity Graph

The exploitability of CVE-2025-54137 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2025-54137

With low attack complexity and no required privileges, CVE-2025-54137 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2025-54137, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2025-54137, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: Low
    CVE-2025-54137 could lead to minor leaks of non-critical information without major privacy breaches.
  • Integrity: Low
    Exploiting CVE-2025-54137 may cause minor changes to data without severely impacting its accuracy.
  • Availability: Low
    CVE-2025-54137 may slightly degrade system performance without fully affecting service availability.

CVE-2025-54137 References

External References

CWE Common Weakness Enumeration

CWE-1392

Vulnerable Configurations

  • cpe:2.3:a:psu:haxcms-nodejs:0.0.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:0.0.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:0.0.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:0.0.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:0.0.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:0.0.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:0.0.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:0.0.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:0.0.7:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:0.0.7:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:0.0.8:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:0.0.8:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:0.0.9:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:0.0.9:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:0.0.10:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:0.0.10:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:0.0.11:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:0.0.11:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:0.0.12:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:0.0.12:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:0.0.13:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:0.0.13:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:0.0.14:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:0.0.14:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:0.0.15:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:0.0.15:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:0.0.16:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:0.0.16:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:0.0.17:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:0.0.17:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:0.0.18:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:0.0.18:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:0.0.19:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:0.0.19:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:9.0.0:-:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:9.0.0:-:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:9.0.0:alpha0:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:9.0.0:alpha0:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:9.0.0:alpha1:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:9.0.0:alpha1:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:9.0.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:9.0.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:9.0.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:9.0.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:9.0.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:9.0.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:9.0.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:9.0.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:9.0.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:9.0.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:9.0.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:9.0.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:9.0.7:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:9.0.7:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:9.0.8:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:9.0.8:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:9.0.9:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:9.0.9:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:9.0.10:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:9.0.10:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:9.0.11:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:9.0.11:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:9.0.12:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:9.0.12:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:9.0.13:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:9.0.13:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:9.0.14:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:9.0.14:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:9.0.15:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:9.0.15:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:9.0.16:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:9.0.16:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:9.0.17:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:9.0.17:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:9.0.18:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:9.0.18:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:9.0.19:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:9.0.19:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:9.0.20:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:9.0.20:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:9.0.21:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:9.0.21:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:10.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:10.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:10.0.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:10.0.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:10.0.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:10.0.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:10.0.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:10.0.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:10.0.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:10.0.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:10.0.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:10.0.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:10.0.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:10.0.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:11.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:11.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:11.0.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:11.0.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:11.0.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:11.0.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:11.0.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:11.0.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:11.0.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:11.0.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:11.0.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:11.0.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:11.0.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:11.0.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:11.0.7:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:11.0.7:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:11.0.8:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:11.0.8:*:*:*:*:node.js:*:*
  • cpe:2.3:a:psu:haxcms-nodejs:11.0.9:*:*:*:*:node.js:*:*
    cpe:2.3:a:psu:haxcms-nodejs:11.0.9:*:*:*:*:node.js:*:*

Protect Your Infrastructure against CVE-2025-54137: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-48042 – Incorrect Authorization vulnerability in ash-project ash allows Exploiting Incorrectly Configured Access Control Security Levels. This vulnerabilit...
  • CVE-2025-39734 – In the Linux kernel, the following vulnerability has been resolved: Revert "fs/ntfs3: Replace inode_trylock with inode_lock" This reverts commit ...
  • CVE-2025-39733 – In the Linux kernel, the following vulnerability has been resolved: team: replace team lock with rtnl lock syszbot reports various ordering issue...
  • CVE-2025-39732 – In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: fix sleeping-in-atomic in ath11k_mac_op_set_bitrate_mask() ath1...
  • CVE-2025-39731 – In the Linux kernel, the following vulnerability has been resolved: f2fs: vm_unmap_ram() may be called from an invalid context When testing F2FS ...