dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-46394

HIGH · 7.7 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 →
83/100
Remediation priority · High
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 OS command injection vulnerability exists in the Git.php library of the HAXcms PHP backend. The application constructs shell command strings using unsanitized input and executes them via proc_open(). An attacker who can control parameters passed into Git operations can execute arbitrary OS commands with the privileges of the web server. Out of 17 functions that invoke shell commands only 1 function (`commit()`) correctly uses `escapeshellarg()`. When combined with another vulnerability that allows configuration manipulation, this issue can lead to full remote code execution and complete system compromise. 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

OS command injection vulnerability in HAXcms PHP backend's Git.php library where 16 of 17 shell command functions fail to sanitize input before passing to proc_open(). An attacker with control over Git operation parameters can execute arbitrary OS commands with web server privileges, potentially achieving full RCE when chained with a configuration manipulation vulnerability.

MitigationUpgrade to HAXcms version 26.0.0 which patches the issue by implementing proper input sanitization across all Git library functions.

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

CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/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. Confirm HAXcms installation
    Locate the HAXcms installation by checking for the main index.php or autoloader file in the web root directory. Common paths include /var/www/html/haxcms or similar web-accessible directories.
    Affected if HAXcms is present on the server
  2. Identify Git.php library location
    Find the Git.php file in the HAXcms codebase, typically located in a /system/lib/ or /libraries/ directory. Search for files named Git.php containing proc_open() calls.
    Affected if The Git.php file exists in the HAXcms installation
  3. Check HAXcms version
    Open the version file or composer.json in the HAXcms root directory to read the installed version number. Compare it against the fixed version 26.0.0.
    Affected if The installed version is below 26.0.0
  4. Inspect vulnerable Git functions
    Examine the Git.php file and look for shell command functions that use proc_open() without proper input sanitization (such as escapeshellarg or escapeshellcmd). Check functions like gitAdd, gitCommit, gitPush, gitPull, gitClone, gitBranch, gitStatus, gitLog, gitDiff, gitFetch, gitMerge, gitRebase, gitTag, gitCheckout, gitReset, and gitStash.
    Affected if The Git.php functions pass user-controlled input to proc_open() without sanitization
  5. Verify Git operations are accessible
    Check if the Git functionality is enabled and accessible to users through the HAXcms API endpoints or web interface. Look for routes or endpoints that trigger Git.php functions.
    Affected if Git operations are exposed and accessible to users or attackers

If HAXcms is installed with the Git.php library present and the version is below 26.0.0 with unsanitized Git function inputs accessible to users, the environment is vulnerable to command injection.

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 which patches the issue by implementing proper input sanitization across all Git library functions.

Recommended fix High confidence

26.0.0

  1. 1. Identify the current installed version of HAXcms PHP backend by examining the version file or composer.json
  2. 2. If running a version prior to 26.0.0, plan for upgrade to version 26.0.0 or later
  3. 3. Backup the entire HAXcms installation including database and configuration files
  4. 4. Download HAXcms version 26.0.0 or the latest stable release from the official repository
  5. 5. Replace the existing installation files with the new version, preserving custom configurations
  6. 6. Verify the Git.php library has been updated - it should now use escapeshellarg() for all shell command invocations
  7. 7. Test Git-related operations (clone, pull, push, commit, etc.) to confirm functionality
  8. 8. Monitor logs for any command injection attempts that may have occurred prior to patching

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,180
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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