← Back
CVE-2026-48527
high
CVSS 8.7
Cross-Site Scripting (XSS) in @haxtheweb/haxcms-nodejs (CVE-2026-48527)
Summary
cross-site scripting in @haxtheweb/haxcms-nodejs (CVE-2026-48527). Confidential information can be exposed externally. Exploitable via `POST /system/api/saveNode`. Mitigation: upgrade to `26.0.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-48527** has been found in @haxtheweb/haxcms-nodejs.
Attackers can target a specific entry point like `POST /system/api/saveNode` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.7/10.
What to do: upgrade @haxtheweb/haxcms-nodejs to **26.0.1** or later.
If unsure, ask your IT team or search "@haxtheweb/haxcms-nodejs CVE-2026-48527" on the vendor's site.
CVE-2026-48527 (@haxtheweb/haxcms-nodejs) — CWE-79 / CVSS v3 8.7
Attack vector: remote (network-reachable)
Attack surface: POST /system/api/saveNode / `onclick` / `node.body` / `index.html`
Patched: `26.0.1` — 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.
❓ What is the problem
**Cross-site scripting (XSS)** (CWE-79) exists in @haxtheweb/haxcms-nodejs. Attackers reach the vulnerable code path via `POST /system/api/saveNode` without authentication.
📍 Affected scope
@haxtheweb/haxcms-nodejs — . Attack surface: POST /system/api/saveNode / `onclick` / `node.body` / `index.html`.
🔥 Severity
Severity: High (CVSS 8.7/10). Confidential information can be exposed externally
🔧 How to fix
Update to **26.0.1**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual `POST /system/api/saveNode` requests with malformed payloads or SQL meta-characters. Run `grep -r '@haxtheweb/haxcms-nodejs' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'POST /system/api/saveNode' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `POST /system/api/saveNode` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade @haxtheweb/haxcms-nodejs to 26.0.1ステージング環境で 26.0.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against POST /system/api/saveNode on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@haxtheweb/haxcms-nodejs
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"26.0.1"}]}]