CVE-2026-46496: HAX CMS: Stored XSS via '<video-player>' component allows arbitrary JavaScript execution and token theft
Summary A stored cross-site scripting (XSS) vulnerability exists in HAX CMS 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.
Published May 19, 2026 · Updated Jun 9, 2026
Affected packages
@haxtheweb/haxcms-nodejs
- Ecosystem
- npm
- Affected
- <= 25.0.0
- Fixed in
- 26.0.0
- Check
npm ls @haxtheweb/haxcms-nodejs
@haxtheweb/video-player
- Ecosystem
- npm
- Affected
- <= 25.0.0
- Fixed in
- 26.0.0
- Check
npm ls @haxtheweb/video-player
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
A stored cross-site scripting (XSS) vulnerability exists in HAX CMS due to improper sanitization of the <video-player> 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.
Details
The vulnerability is present in the <video-player> web component used within the HAX CMS editor.
The application fails to validate or sanitize user-supplied input in the following attributes:
sourcesource-data
These attributes accept arbitrary URI schemes, including javascript:, which leads to execution of attacker-controlled JavaScript in the browser.
Example vulnerable usage:
<video-player
source="javascript:alert(document.domain)"
source-type="external">
</video-player>Because this content is stored and rendered to other users, the vulnerability is classified as a stored XSS.
The root cause is the lack of URI scheme validation and improper sanitization of component attributes before rendering. Because this content is stored and rendered to other users, the vulnerability is classified as a stored XSS.
The root cause is the lack of URI scheme validation and improper sanitization of component attributes before rendering.
PoC
Steps to reproduce:
- Log in to HAX CMS as user.
- Create a website or any page and switch to the HTML source editor (
<>). - Insert the following payload:
<video-player source="javascript:alert('JWT: '+localStorage.getItem('jwt').substring(0,30))" source-type="external"></video-player>Save the page.
Reload or revisit or send the page.
Result
A JavaScript alert executes. The JWT token is exposed. This confirms arbitrary JavaScript execution in the victim’s browser.
Impact
This vulnerability allows stored XSS leading to:
- Theft of JWT authentication tokens
- Session hijacking
- Full account takeover
- Execution of arbitrary JavaScript in victim browsers
If an administrator views a malicious page, this can lead to full CMS compromise.
Attack complexity: Low Privileges required: Low (any authenticated user) User interaction: Required
Credited to trigerman.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-48527
HaxCMS has a stored Cross-Site Scripting (XSS) bypass in its saveNode endpoint
high8.7May 29, 2026CVE-2026-46357
HAX CMS: Denial of Service using Malicious Import Request
medium6.5May 19, 2026CVE-2026-46393
HAXcms createSite SSRF Enables Arbitrary File Read
high7.1May 19, 2026CVE-2026-46395
HAXcms: Private Key Disclosure via Broken HMAC Implementation
critical9.3May 19, 2026CVE-2026-46396
Stored XSS via <iframe> in HAX CMS allows access to sensitive client-side data and account takeover
high8.6May 19, 2026CVE-2026-46511
HAXcms: Mass Token Exfiltration and Cross-Tenant Hijack
high8.7May 19, 2026
