Vulnerability in @haxtheweb/haxcms-nodejs (CVE-2026-46511)
Summary
Vulnerability in @haxtheweb/haxcms-nodejs (CVE-2026-46511). Risk of unauthorized operations or information disclosure. Exploitable via jwt. Mitigation: upgrade to 26.0.0 or later.
Original description
The description as published by the source.
Summary
An attack chain utilizing Stored XSS alongside dynamic token exposure in the /system/api/connectionSettings endpoint allows an authenticated attacker to perform a complete cross-tenant account takeover. The API dynamically leaks the active session's authentication tokens (including the jwt, user_token, site_token, and appstore_token) into a global JavaScript variable (window.appSettings). An attacker can exploit the XSS vulnerability to force a victim's browser to silently fetch their specific connection settings, extract the tokens, and exfiltrate them to an attacker-controlled webhook.
Details
In Operations.php (connectionSettings()), the system returns a Javascript object designed to bootstrap the frontend context. This object, window.appSettings, acts as a "skeleton key" because it aggregates all necessary operational tokens for the active session.
While HAXcms correctly relies on the cryptographically signed JWT for backend authentication (preventing Direct Object Reference/IDOR attempts), the CMS fails to secure the tokens themselves. Specifically:
- The Vector: The system is vulnerable to Stored XSS (e.g., via injected
iframesrcdocor ``). - The Exposure: Because the
connectionSettingsendpoint serves the tokens locally based on the activePHPSESSIDcookie, any malicious script running in the browser context can intercept these keys. - The Chain: HAXcms isolates user environments by URL path (
//). An at…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-46511 has been found in @haxtheweb/haxcms-nodejs.
Attackers can target a specific entry point like jwt over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade @haxtheweb/haxcms-nodejs to 26.0.0 or later.
If unsure, ask your IT team or search "@haxtheweb/haxcms-nodejs CVE-2026-46511" on the vendor's site.
CVE-2026-46511 (@haxtheweb/haxcms-nodejs) — CWE-522
Attack surface: jwt / user_token / site_token / appstore_token
Patched: 26.0.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-522) exists in @haxtheweb/haxcms-nodejs. Attackers reach the vulnerable code path via jwt.
Check the vendor advisory for the affected versions of @haxtheweb/haxcms-nodejs. Attack surface: jwt / user_token / site_token / appstore_token.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 26.0.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@haxtheweb/haxcms-nodejs' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@haxtheweb/haxcms-nodejs' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@haxtheweb/haxcms-nodejsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @haxtheweb/haxcms-nodejs to 26.0.0ステージング環境で 26.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com