Severity by source
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Primary rating from GitHub Advisory · only source for this CVE.
CVSS VectorGitHub Advisory
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Lifecycle Timeline
6Blast Radius
ecosystem impact- 30 npm packages depend on @haxtheweb/iframe-loader (4 direct, 26 indirect)
- 24 npm packages depend on @haxtheweb/video-player (6 direct, 18 indirect)
Ecosystem-wide dependent count for version 26.0.0 and other introduced versions.
DescriptionGitHub Advisory
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><img width="2446" height="1319" alt="image" src="https://github.com/user-attachments/assets/daea3b41-8c72-4f6c-ab32-34c688bbd251" />
<img width="2464" height="1397" alt="image" src="https://github.com/user-attachments/assets/911cbd42-db50-454a-b178-51555e0db79c" />
<img width="2466" height="1409" alt="webhook`" src="https://github.com/user-attachments/assets/8a286435-98f4-418c-a596-d0c19556696a" />
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.
AnalysisAI
Stored cross-site scripting in HAX CMS (versions <= 25.0.0) allows authenticated users to inject malicious <iframe> elements with javascript: URIs or srcdoc payloads that execute in viewers' browsers, enabling theft of JWTs exposed via window.appSettings and full account takeover. A working proof-of-concept is published in the GHSA advisory demonstrating JWT exfiltration, and a vendor patch is available in 26.0.0. No public exploit identified at time of analysis beyond the published PoC, and the issue is not listed in CISA KEV.
Technical ContextAI
HAX CMS is a headless/decoupled content management system built as a collection of npm packages (notably @haxtheweb/haxcms-nodejs, @haxtheweb/video-player, and @haxtheweb/iframe-loader) that lets authenticated authors edit page HTML directly through a source editor. The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation): the HTML sanitizer permits <iframe> elements and does not strip javascript: URIs from src attributes or block dangerous srcdoc content with allow-scripts allow-same-origin sandbox tokens. Because the front-end stores sensitive material such as JWTs on window.appSettings, scripts executing in the same origin can read authentication tokens directly from the DOM rather than relying on cookie theft.
RemediationAI
Vendor-released patch: upgrade @haxtheweb/haxcms-nodejs, @haxtheweb/video-player, and @haxtheweb/iframe-loader to 26.0.0 or later per GHSA-jh3h-rpxg-fr36 (https://github.com/haxtheweb/issues/security/advisories/GHSA-jh3h-rpxg-fr36). Until the upgrade is deployed, restrict page-editing privileges to fully trusted users and audit existing page content for <iframe> tags containing javascript: URIs or srcdoc attributes; consider temporarily disabling the raw HTML source editor (<>) in the authoring UI, which prevents the injection vector at the cost of removing direct HTML editing for authors. As a defensive hardening step independent of this CVE, stop exposing the JWT on window.appSettings (move it to an HttpOnly cookie) so that future client-side script execution cannot trivially exfiltrate session credentials; this is a substantive architectural change and should be tested against any client code that currently reads the token from the global.
Same weakness CWE-79 – Cross-site Scripting (XSS)
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-34891
GHSA-jh3h-rpxg-fr36