# CVE-2026-46496: HAX CMS: Stored XSS via '' component allows arbitrary JavaScript execution and token theft > Attackers can execute arbitrary JavaScript and steal JWT tokens via stored XSS in the video-player component of HAX CMS. - **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 5 Jun 2026 - **Updated:** 5 Jun 2026 - **Also known as:** GHSA-2m6p-hm3w-6jm3 ## What is CVE-2026-46496? CVE-2026-46496 is a critical cross-site scripting vulnerability in haxtheweb haxcms-nodejs, published on 5 Jun 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. ### Official description HAX CMS helps manage microsite universe with PHP or NodeJs backends. A stored cross-site scripting (XSS) vulnerability exists in versions prior to 26.0.0 due to improper sanitization of the `` component. The component allows `javascript:` URIs in the `source` attribute, which are executed when the page is viewed. This enables attackers to execute arbitrary JavaScript in the context of the victim’s browser and access sensitive data such as JWT tokens and more. Version 26.0.0 fixes the issue. Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-116 (Improper Encoding or Escaping of Output) ## Which versions are affected by CVE-2026-46496? 4 open source packages ship an affected version, including @haxtheweb/haxcms-nodejs and @haxtheweb/video-player. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `@haxtheweb/haxcms-nodejs` | npm | All versions | 26.0.0 | | `@haxtheweb/haxcms-nodejs` | npm | All versions | 26.0.0 | | `@haxtheweb/video-player` | npm | All versions | 26.0.0 | | `@haxtheweb/video-player` | npm | All versions | 26.0.0 | ## How do I fix CVE-2026-46496? Upgrade @haxtheweb/haxcms-nodejs to 26.0.0 or later. ## Is CVE-2026-46496 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46496 exists. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-46496 and fix it if it is affected. What it is: CVE-2026-46496 is a critical cross-site scripting vulnerability in haxtheweb haxcms-nodejs, published on 5 Jun 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46496 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 - @haxtheweb/video-player (npm): affected all versions; fixed in 26.0.0 - @haxtheweb/video-player (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-46496/ (Markdown: https://insights.sbomify.com/CVE-2026-46496/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-46496 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-46496 - OSV: https://osv.dev/vulnerability/CVE-2026-46496 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-46496/ Summaries are generated and may contain mistakes; the official description above is the record.