dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-46397

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, an Authenticated Local File Inclusion (LFI) vulnerability in the HAXCMS saveOutline endpoint allows a low-privileged user to read arbitrary files on the server by manipulating the location field written into site.json. This enables attackers to exfiltrate sensitive system files such as /etc/passwd, application secrets, or configuration files accessible to the web server (www-data). Version 26.0.0 patches 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

Authenticated Local File Inclusion (LFI) vulnerability in HAXCMS saveOutline endpoint allows low-privileged authenticated users to read arbitrary server files by manipulating the 'location' field written into site.json, enabling exfiltration of sensitive files like /etc/passwd and configuration files.

MitigationUpgrade to HAXCMS version 26.0.0 or later to patch the vulnerability.

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
High
Integrity
None
Availability
None

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

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 HAXCMS installation and version
    Locate the HAXCMS installation directory and check the version indicator (such as a version.php file, composer.json, or package.json in the root directory). Compare the version number to the affected range: versions prior to 26.0.0 are vulnerable.
    Affected if The installed version is earlier than 26.0.0
  2. Verify saveOutline endpoint exists
    Check for the saveOutline endpoint file or route in the HAXCMS installation, typically in the API or backend routes directory. Look for files handling the saveOutline functionality.
    Affected if The saveOutline endpoint exists and is accessible without additional security controls
  3. Inspect site.json file permissions and location
    Locate the site.json file within the HAXCMS data or sites directory. Verify file permissions and check if the web server process (www-data) has write access to this file.
    Affected if site.json is writable by the web server user, allowing manipulation of the location field
  4. Check authentication controls on saveOutline
    Review the authentication and authorization settings for the saveOutline endpoint. Determine whether low-privileged or unauthenticated users can access and manipulate the location parameter.
    Affected if Low-privileged authenticated users can access the endpoint and modify the location parameter without proper path sanitization

A system is affected if it runs HAXCMS version earlier than 26.0.0 with the saveOutline endpoint accessible to low-privileged users and site.json writable by the web server process.

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 HAXCMS version 26.0.0 or later to patch the vulnerability.

Recommended fix High confidence

26.0.0

  1. 1. Back up your current HAXCMS installation and database before upgrading.
  2. 2. Upgrade HAXCMS to version 26.0.0 or later by following the official upgrade documentation for your backend (PHP or NodeJS).
  3. 3. After upgrading, verify that the saveOutline endpoint properly sanitizes the location field and no longer accepts path traversal sequences (e.g., ../../).
  4. 4. Review application logs for any signs of exploitation attempts targeting this vulnerability prior to the upgrade.
  5. 5. If feasible, test the upgrade in a staging environment first to ensure compatibility with your existing site configurations.
Caveat Review HAXCMS release notes for version 26.0.0 to check for any breaking changes specific to your configuration before deploying to production.

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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