CVE-2026-48527: HaxCMS has a stored Cross-Site Scripting (XSS) bypass in its saveNode endpoint
Summary HaxCMS is affected by a stored cross-site scripting (XSS) vulnerability in the /system/api/saveNode endpoint. An authenticated user with a permission to edit pages can bypass the HTML sanitizer by injecting an event handler attribute without whitespace before the attribute name.
Published May 29, 2026 · Updated Jun 9, 2026
Affected packages
@haxtheweb/haxcms-nodejs
- Ecosystem
- npm
- Affected
- <= 26.0.0
- Fixed in
- 26.0.1
- Check
npm ls @haxtheweb/haxcms-nodejs
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
HaxCMS is affected by a stored cross-site scripting (XSS) vulnerability in the /system/api/saveNode endpoint. An authenticated user with a permission to edit pages can bypass the HTML sanitizer by injecting an event handler attribute without whitespace before the attribute name.
For example, the sanitizer misses:
click meThe important bypass is:
href="#"onclick=The payload is stored in the generated page files and executes when a user clicks the injected link.
Details
The issue is caused by regex-based HTML sanitization that expects whitespace before event handler attributes. Because the sanitizer expects a pattern like:
href="#" onclick="..."It fails to remove an event handler when it is written without whitespace:
href="#"onclick="..."Browsers still parse onclick as a valid event handler attribute, so the JavaScript executes when the element is clicked.
Affected endpoint:
POST /system/api/saveNode?site_token=[VALID_SITE_TOKEN]Affected parameter:
node.bodyPoC
- Log in to HaxCMS and edit any existing page.
- Capture the page save request in Burp Suite:
POST /system/api/saveNode?site_token=[VALID_SITE_TOKEN]- In the JSON request body, modify only the
node.bodyvalue.
Change:
"body":"...existing page content...\n"To:
"body":"...existing page content...\nclick me\n"- Forward the request.
- Open the edited page and click
click me.
Result:
The JavaScript will execute and the alert will pop up.
It was confirmed that the payload is stored in the generated page files, including index.html.
Impact
An authenticated user with permissions to edit the page can inject stored JavaScript into the page content. If a privileged user interacts with the injected element while authenticated, the attacker controlled JavaScript will execute in that user’s browser.
Based on local testing, the XSS can access browser-exposed HaxCMS data such as localStorage.jwt and window.appSettings, including API paths and tokens available to the authenticated user.
This may allow an attacker to perform actions as the victim within the limits of the exposed tokens and the victim’s permissions and possibly chain more vulnerabilities.
Credited to kn1ph.
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-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-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
