CVE-2026-46396: Stored XSS via <iframe> in HAX CMS allows access to sensitive client-side data and account takeover
Summary A stored cross-site scripting (XSS) vulnerability exists in HAX CMS due to improper sanitization of elements. The application allows javascript: URIs in the src attribute, which are executed when a malicious page is viewed. This enables attackers to execute arbitrary JavaScript in the context of the victim’s browser and access sensitive data exposed to client-side scripts.
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
@haxtheweb/iframe-loader
- Ecosystem
- npm
- Affected
- <= 25.0.0
- Fixed in
- 26.0.0
- Check
npm ls @haxtheweb/iframe-loader
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 <iframe> elements.
The application allows javascript: URIs in the src attribute, which are executed when a malicious page is viewed. This enables attackers to execute arbitrary JavaScript in the context of the victim’s browser and access sensitive data exposed to client-side scripts.
Details
Successful exploitation allows access to any data available in the browser context, including:
- Authentication tokens (e.g., JWT)
- Session cookies (if not protected with HttpOnly)
- Application configuration (e.g., window.appSettings)
- User-specific data accessible via APIs
This significantly increases the impact beyond simple script execution.
PoC
Steps to reproduce:
- Log in to HAX CMS as any authenticated user.
- Create a new page or edit an existing page.
- Open the HTML source editor (
<>). - Insert the following payload:
<iframe srcdoc="<script>
(function(){
try {
var jwt = parent.window.appSettings.jwt;
alert('Stolen JWT:\n' + jwt);
} catch(e) {
alert('Error: ' + e.message);
}
})();
</script>" style="display:none" sandbox="allow-scripts allow-same-origin"></iframe>Impact
This vulnerability allows stored XSS leading to:
- Execution of arbitrary JavaScript in victim browsers
- Access to sensitive client-side data, including authentication tokens and session identifiers
- Unauthorized API actions performed on behalf of the victim
- Session hijacking and full account takeover
Because the application exposes authentication data in the client-side environment, exploitation of this vulnerability can lead to complete compromise of user accounts and site content.
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-46496
HAX CMS: Stored XSS via '<video-player>' component allows arbitrary JavaScript execution and token theft
medium5.1May 19, 2026CVE-2026-46511
HAXcms: Mass Token Exfiltration and Cross-Tenant Hijack
high8.7May 19, 2026
