CVE-2026-46393
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 · uneditedHAX CMS helps manage microsite universe with PHP or NodeJs backends. An authenticated Server-Side Request Forgery (SSRF) vulnerability in versions prior to 26.0.0 allows authenticated users to fetch arbitrary internal or local resources and write the responses to a web-accessible directory, enabling arbitrary file read and internal network access. Version 26.0.0 contains a fix.
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 confidenceAuthenticated SSRF in HAX CMS allows authenticated users to cause the server to make arbitrary requests to internal/local resources and write the responses to web-accessible directories, enabling arbitrary file read and internal network access.
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: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 checksWork through these to decide whether this CVE applies to you.
-
Confirm HAX CMS installationSearch the web server document root for HAX CMS-specific files, directories, or signature files that indicate HAX CMS is presentAffected if HAX CMS is found in the environment
-
Locate version informationCheck for version files, package.json, composer.json, or application configuration that stores the HAX CMS version numberAffected if Version information cannot be located or is inconsistent across version sources
-
Compare version to fixed releaseCompare the identified installed version against version 26.0.0 - the version containing the fixAffected if Installed version is any version prior to 26.0.0
-
Verify authenticated access existsConfirm that user authentication is enabled and user accounts can access the HAX CMS applicationAffected if Authenticated user accounts can access the application and trigger URL-based features
Environment is affected if HAX CMS is present with a version lower than 26.0.0 and authenticated users can access endpoints capable of making outbound requests to arbitrary URLs
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to version 26.0.0 or later to obtain the fix; if immediate upgrade is not feasible, implement strict validation of user-supplied URLs in authenticated endpoints and restrict network access from the application server to internal resources.
26.0.0
- 1. Back up your current HAX CMS installation including database and all configuration files
- 2. Download HAX CMS version 26.0.0 from the official GitHub repository (github.com)
- 3. Review the upgrade instructions provided in the release notes or documentation
- 4. Replace the existing installation files with the new version 26.0.0 files
- 5. Run any database migration scripts if required by the upgrade
- 6. Verify the installation was successful by logging in and testing core functionality
- 7. Confirm the SSRF vulnerability is remediated by verifying that internal/local resource fetching is no longer possible
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46393 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-46393 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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