dbcve.org
CWE-15Weakness · CWE-15

CVE-2026-46399

CRITICAL · 9.4 CVSS v4.0 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 →
100/100
Remediation priority · Urgent
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. The PHP version of HAX CMS prior to version 26.0.0 has an authenticated file overwrite vulnerability. An attacker can exploit this vulnerability to configure malicious Git filter commands and achieve code execution on the HAX CMS server. 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

HAX CMS PHP versions before 26.0.0 have an authenticated file overwrite vulnerability allowing attackers to configure malicious Git filter commands, leading to remote code execution on the server.

MitigationUpgrade HAX CMS PHP to version 26.0.0 or later. Additionally, review and audit Git filter configurations and user accounts to ensure no malicious filters were previously installed.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 PHP installation
    Look for HAX CMS directories on the web server. Common paths include /var/www/html/, /home/*/public_html/, or the web root. Search for files containing 'HAX' or 'haxcms' in filenames, particularly index.php or configuration files.
    Affected if HAX CMS PHP is present on the server
  2. Determine installed version
    Locate the version file or check the main index.php for a version string. Common locations: /includes/version.php, /version.json, or the root composer.json. Compare the version number to 26.0.0 using semantic versioning.
    Affected if Installed version is before 26.0.0 (e.g., 25.x, 24.x, etc.)
  3. Verify administrative access is enabled
    Check if the /admin or /login endpoint is accessible on the web server. Confirm that authentication is not restricted to localhost only or behind a VPN. Inspect the web server access logs for recent admin panel access.
    Affected if Administrative interface is publicly accessible without network restrictions
  4. Inspect Git configuration files
    Check for .git/config files within the HAX CMS installation directory and any Git repositories. Look for modifications to the [filter] section. Inspect /etc/gitconfig, ~/.gitconfig, and the repository-specific .git/config for unexpected filter definitions.
    Affected if Git filter configuration contains unexpected or suspicious commands, particularly lfs or diff filters pointing to unfamiliar executables or scripts

Environment is affected if HAX CMS PHP versions before 26.0.0 are installed with the admin interface accessible, regardless of whether Git configuration changes are currently observable.

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 HAX CMS PHP to version 26.0.0 or later. Additionally, review and audit Git filter configurations and user accounts to ensure no malicious filters were previously installed.

Recommended fix High confidence

26.0.0

  1. Backup your current HAX CMS installation and database before proceeding
  2. Verify your current HAX CMS PHP version is below 26.0.0 by checking the admin panel or version file
  3. Download HAX CMS version 26.0.0 from the official GitHub repository (github.com)
  4. Replace the existing HAX CMS files with the new version 26.0.0 files, preserving your configuration and content
  5. Verify file permissions are correctly set after the upgrade
  6. Test that the admin login works and the application functions normally
  7. Confirm the upgrade was successful by checking the new version number in the admin interface
Caveat No specific breaking changes mentioned in the provided description; standard upgrade precautions apply

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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