dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2026-46357

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
HAX CMS helps manage microsite universe with PHP or NodeJs backends. Prior to version 26.0.0, the HAX CMS NodeJS application crashes when an authenticated attacker sends a specially crafted site creation request to the createSite endpoint. A single request is sufficient to take the entire application offline, requiring a manual server restart to restore service. Version 26.0.0 fixes the issue.

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

HAX CMS NodeJS versions prior to 26.0.0 contain a denial-of-service vulnerability in the createSite endpoint where a specially crafted site creation request from an authenticated attacker causes the application to crash. The crash is severe enough that automatic recovery does not occur, requiring manual server restart to restore service.

MitigationUpgrade to HAX CMS NodeJS version 26.0.0 or later. In the meantime, restrict access to the createSite endpoint to only trusted authenticated users and monitor for service interruptions.

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

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Identify HAX CMS NodeJS version
    Locate the package.json file in the HAX CMS installation directory and check the version field, or run 'npm list hax-cms' or 'node -e "require("./package.json").version"' from the installation root
    Affected if The version is lower than 26.0.0 (e.g., 25.x.x, 24.x.x, etc.)
  2. Confirm createSite endpoint exists
    Check if the createSite route is defined in the application routes or API endpoint configuration files (typically in the routes or api directory)
    Affected if The createSite endpoint is defined and available in the codebase
  3. Verify authentication is enabled for the endpoint
    Review the authentication middleware applied to the createSite route in the route definition or server configuration to confirm it accepts authenticated users
    Affected if The endpoint accepts requests from authenticated users (even if restricted to certain roles)
  4. Check if the server is currently reachable
    Send a health check request or attempt to access any public API endpoint to confirm the application is running
    Affected if The application is running and accessible (indicating the DoS condition could be triggered)

The environment is affected if HAX CMS NodeJS version is below 26.0.0 AND the createSite endpoint is accessible to authenticated users, as a single crafted request could crash the entire application.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to HAX CMS NodeJS version 26.0.0 or later. In the meantime, restrict access to the createSite endpoint to only trusted authenticated users and monitor for service interruptions.

Recommended fix High confidence

Version 26.0.0

  1. 1. Identify the current HAX CMS NodeJS backend version in use
  2. 2. Plan and schedule a maintenance window for the upgrade
  3. 3. Backup the current HAX CMS installation, including configuration files and database
  4. 4. Upgrade HAX CMS NodeJS backend to version 26.0.0 or later
  5. 5. Verify the upgrade was successful by checking the version number
  6. 6. Test the createSite endpoint functionality
  7. 7. Monitor application logs to ensure stability after upgrade

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46357 — 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-2026-46357 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