# CVE-2026-46511: HAXcms: Mass Token Exfiltration and Cross-Tenant Hijack

> An authenticated attacker can exploit Stored XSS to steal session tokens from the connection settings API, leading to cross-tenant account takeover.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/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-x3x5-7h4h-gwxg

## What is CVE-2026-46511?

CVE-2026-46511 is a high-severity cross-site scripting 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. Prior to version 26.0.0, an attack chain utilizing Stored XSS alongside dynamic token exposure in the `/system/api/connectionSettings` endpoint allows an authenticated attacker to perform a complete cross-tenant account takeover. The API dynamically leaks the active session's authentication tokens (including the `jwt`, `user_token`, `site_token`, and `appstore_token`) into a global JavaScript variable (`window.appSettings`). An attacker can exploit the XSS vulnerability to force a victim's browser to silently fetch their specific connection settings, extract the tokens, and exfiltrate them to an attacker-controlled webhook. Version 26.0.0 patches the issue.

Weakness: CWE-922 (Insecure Storage of Sensitive Information), CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-522 (Insufficiently Protected Credentials)

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

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-46511?

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

## Is CVE-2026-46511 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-46511 is a high-severity cross-site scripting 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-46511 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-46511/ (Markdown: https://insights.sbomify.com/CVE-2026-46511/index.md)
```

## Sources

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

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