SSRF (Server-Side Request Forgery) in @haxtheweb/haxcms-nodejs (CVE-2026-46393)
Summary
SSRF in @haxtheweb/haxcms-nodejs (CVE-2026-46393). Risk of unauthorized operations or information disclosure. Exploitable via POST /createSite. Mitigation: upgrade to 26.0.0 or later.
Original description
The description as published by the source.
Summary
An authenticated Server-Side Request Forgery (SSRF) vulnerability in HAXcms allows users to fetch arbitrary internal or local resources and write the responses to a web-accessible directory, enabling arbitrary file read and internal network access.
Details
The createSite endpoint in HAXcms (v11.0.6) accepts a build.files parameter that allows an authenticated user to supply arbitrary URLs or local file paths. This input is processed without validation and ultimately fetched server-side using file_get_contents().
The data flow is as follows:
- User input (
build.files) is processed viaobject_to_array()into a PHP array - Assigned to
$filesToDownloadinOperations.php(line 2626) - Iterated over in
Operations.php(line 2730), where each entry is passed toHAXCMSFile::save()with bulk-import enabled
In HAXCMSFile.php (line 30), the following occurs:
file_get_contents($upload['tmp_name']);
Here, tmp_name is attacker-controlled and may contain:
- External URLs (
http://attacker.com) - Internal services (
http://127.0.0.1) - Cloud metadata endpoints (
http://169.254.169.254) - Local file paths (
/etc/passwd,/proc/self/environ)
The bulk-import flag bypasses is_uploaded_file() validation, which normally ensures the file originates from a legitimate upload. The only restriction is an extension whitelist based on the filename (array key), which is fully attacker-controlled.
There are no restrictions on:
- URL sch…
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-46393 has been found in @haxtheweb/haxcms-nodejs.
Attackers can target a specific entry point like POST /createSite 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-46393" on the vendor's site.
CVE-2026-46393 (@haxtheweb/haxcms-nodejs) — CWE-918
Attack surface: POST /createSite / GET /sites/poc/files/poc.txt / createSite / build.files
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.
SSRF (CWE-918) exists in @haxtheweb/haxcms-nodejs. Attackers reach the vulnerable code path via POST /createSite.
Check the vendor advisory for the affected versions of @haxtheweb/haxcms-nodejs. Attack surface: POST /createSite / GET /sites/poc/files/poc.txt / createSite / build.files.
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 POST /createSite 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
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 し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /createSite' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /createSiteへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade @haxtheweb/haxcms-nodejs to 26.0.0ステージング環境で 26.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /createSite on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com