# CVE-2026-46393: HAXcms createSite SSRF Enables Arbitrary File Read

> Authenticated attackers can exploit SSRF in HAX CMS to read arbitrary files and access internal networks by writing responses to web-accessible directories.

- **Severity:** High 7.1 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Jun 2026
- **Updated:** 8 Jun 2026
- **Also known as:** GHSA-q862-gcgq-5m6g

## What is CVE-2026-46393?

CVE-2026-46393 is a high-severity server-side request forgery vulnerability in haxtheweb haxcms-nodejs, published on 5 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

HAX 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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-46393?

2 open source packages ship an affected version, including @haxtheweb/haxcms-nodejs.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@haxtheweb/haxcms-nodejs` | npm | All versions | 26.0.0 |
| `@haxtheweb/haxcms-nodejs` | npm | All versions | 26.0.0 |

## How do I fix CVE-2026-46393?

Upgrade @haxtheweb/haxcms-nodejs to 26.0.0 or later.

## Is CVE-2026-46393 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46393 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-46393 and fix it if it is affected.

What it is: CVE-2026-46393 is a high-severity server-side request forgery vulnerability in haxtheweb haxcms-nodejs, published on 5 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46393 exists.

Affected packages and fixed versions:
- @haxtheweb/haxcms-nodejs (npm): affected all versions; fixed in 26.0.0
- @haxtheweb/haxcms-nodejs (npm): affected all versions; fixed in 26.0.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-46393/ (Markdown: https://insights.sbomify.com/CVE-2026-46393/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-46393
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-46393
- OSV: https://osv.dev/vulnerability/CVE-2026-46393

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-46393/
Summaries are generated and may contain mistakes; the official description above is the record.