dbcve.org
Haxcms NodejsApplication · Psu

CVE-2025-54127

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-21
Fix available
A fix is available. Upgrade to 11.0.7 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

HAXcms NodeJS backend versions 11.0.6 and below contains an insecure default configuration where HAXCMS_DISABLE_JWT_CHECKS defaults to 'true', completely disabling JWT-based session authentication and authorization checks. This allows unauthenticated attackers to gain full administrative access to the CMS by simply bypassing authentication entirely.

MitigationUpgrade to version 11.0.7 or later and explicitly set HAXCMS_DISABLE_JWT_CHECKS='false' (or remove the variable) in production deployments. Never use default development settings in production environments.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Haxcms NodejsApplication
Affected:< 11.0.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed HAXcms version
    Run 'npm list haxcms' or inspect the package.json file in the HAXcms installation directory to identify the installed version.
    Affected if The installed version is 11.0.6 or below (any version listed as < 11.0.7).
  2. Inspect HAXCMS_DISABLE_JWT_CHECKS environment variable
    Check the environment variables on the server where HAXcms is running. Run 'echo $HAXCMS_DISABLE_JWT_CHECKS' on Linux/Mac or check System Properties > Environment Variables on Windows. Also check any .env files or container orchestration configuration.
    Affected if The variable is set to 'true' or is unset (defaults to 'true' in affected versions).
  3. Verify authentication configuration
    Review the HAXcms configuration files (config.js, settings.json, or equivalent) to see if JWT or session authentication is explicitly enabled or disabled.
    Affected if Authentication checks are disabled or the configuration does not enforce JWT validation.

You are affected if HAXcms version is below 11.0.7 AND HAXCMS_DISABLE_JWT_CHECKS is either set to 'true' or left unset (which defaults to 'true').

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 11.0.7 or later
Fixed in 11.0.7
Interim mitigation

Upgrade to version 11.0.7 or later and explicitly set HAXCMS_DISABLE_JWT_CHECKS='false' (or remove the variable) in production deployments. Never use default development settings in production environments.

Recommended fix High confidence

11.0.7

  1. Upgrade HAXcms Nodejs to version 11.0.7 or later
  2. After upgrading, verify that HAXCMS_DISABLE_JWT_CHECKS is not set to 'true' in production configuration files and environment variables
  3. Ensure proper authentication is enabled for production deployments
  4. Test that JWT-based authentication is functioning correctly after the upgrade
  5. If HAXCMS_DISABLE_JWT_CHECKS was manually set to 'true' in any custom configuration, change it to 'false' or remove the setting

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Haxcms Nodejs Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-54127 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-54127 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data