Vulnerability in @haxtheweb/haxcms-nodejs (CVE-2026-46357)
Summary
Vulnerability in @haxtheweb/haxcms-nodejs (CVE-2026-46357). Risk of unauthorized operations or information disclosure. Exploitable via createSite. Mitigation: upgrade to 26.0.0 or later.
Original description
The description as published by the source.
Summary
The HAX CMS NodeJS application crashes when an authenticated attacker sends a specially crafted site creation request to the createSite endpoint. A single request is sufficient to take the entire application offline, requiring a manual server restart to restore service.
Details
The createSite remote import flow does not complete end-to-end. Instead, the server crashes before the outbound HTTP fetch happens.
The crash occurs because createSite passes a file object without originalname, while HAXCMSFile.save() immediately dereferences tmpFile.originalname.replace(...).
As a result:
- the request reaches privileged code inside
createSite - the server hits the remote file handling path
- the process crashes before
downloadAndSaveFile()performs the outbound request - no imported file is written into the site directory
Affected Resources
- src/routes/createSite.js:176
- src/lib/HAXCMSFile.js:25
- system/api/createSite
PoC
- Obtain a JWT by logging in with valid credentials.
JWT=$(curl -s -X POST 'http://127.0.0.1:3000/system/api/login' \
-H 'Content-Type: application/json' \
-d '{"username":"admin","password":"admin"}' | grep -o '"jwt":"[^"]*"' | head -1 | cut -d'"' -f4)
- Extract the required tokens from the
connectionSettingsendpoint.
SETTINGS=$(curl -s 'http://127.0.0.1:3000/system/api/connectionSettings')
ROOT_TOKEN=$(printf '%s' "$SETTINGS" | grep -o '"token":"[^"]*"' | head -1 | cut -d'"' -f4…
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-46357 has been found in @haxtheweb/haxcms-nodejs.
Attackers can target a specific entry point like createSite over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
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-46357" on the vendor's site.
CVE-2026-46357 (@haxtheweb/haxcms-nodejs) — CWE-20 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: createSite / originalname / connectionSettings
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-20) exists in @haxtheweb/haxcms-nodejs. Attackers reach the vulnerable code path via createSite.
Check the vendor advisory for the affected versions of @haxtheweb/haxcms-nodejs. Attack surface: createSite / originalname / connectionSettings.
Severity: Medium (CVSS 6.5/10). 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