dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-46390

MEDIUM · 6.9 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 →
78/100
Remediation priority · High
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
HAX CMS helps manage microsite universe with PHP or NodeJs backends. Starting in version 2.0.0 and prior to version 26.0.0, the gitlist plugin is exposed to unauthenticated users, allowing unauthenticated browsing of git repositories and git history. 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

The gitlist plugin in HAX CMS versions 2.0.0 through 25.x is accessible to unauthenticated users, allowing public browsing of git repositories and commit history. This exposes potentially sensitive code, credentials, and internal project details.

MitigationUpgrade to HAX CMS version 26.0.0 or later to patch the vulnerability. Alternatively, disable the gitlist plugin if not required for operations.

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/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. Identify HAX CMS installation
    Locate the HAX CMS installation directory or check running services. Look for the core CMS files such as index.php, package.json, or the haxdesktop directory structure.
    Affected if HAX CMS is installed on the system
  2. Determine installed HAX CMS version
    Check the version file or package.json in the HAX CMS root directory. Common locations include version.php, package.json, or a VERSION file in the root directory.
    Affected if The version number is 2.0.0 or higher but lower than 26.0.0 (2.0.0 to 25.x range)
  3. Verify gitlist plugin presence
    Look for the gitlist plugin directory or module within the HAX CMS installation, typically under the modules, plugins, or sites/all directory structure.
    Affected if The gitlist plugin directory or module exists in the installation
  4. Test unauthenticated gitlist access
    Attempt to access the gitlist endpoint directly via HTTP request to paths such as /gitlist, /gitlist/, or the gitlist route on the server without providing any authentication credentials.
    Affected if The gitlist interface loads and displays repositories or commit history without requiring login credentials

A user is affected if HAX CMS version is between 2.0.0 and 25.x, the gitlist plugin is present, and the gitlist endpoint is accessible without authentication.

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 version 26.0.0 or later to patch the vulnerability. Alternatively, disable the gitlist plugin if not required for operations.

Recommended fix High confidence

26.0.0

  1. 1. Backup your current HAX CMS installation and database before proceeding with any upgrade.
  2. 2. Review the official HAX CMS release notes and changelog for version 26.0.0 to understand any configuration or migration requirements.
  3. 3. Download HAX CMS version 26.0.0 or later from the official source (e.g., the GitHub repository or distribution channel).
  4. 4. Update your HAX CMS installation to version 26.0.0 following the standard upgrade procedure for your deployment method (e.g., Composer for PHP backend or npm for NodeJS backend).
  5. 5. After upgrading, verify that the gitlist plugin is no longer accessible to unauthenticated users by attempting to access it without credentials.
  6. 6. Test that legitimate administrative users can still access the gitlist plugin after authentication.
Caveat Review the changelog between your current version and 26.0.0 for potential breaking changes, as this is a significant version jump

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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