HAXcms (<= 25.0.0) — CraftedSignal Threat Feedhttps://feed.craftedsignal.io/products/haxcms--25.0.0/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioTue, 19 May 2026 14:44:52 +0000HAXcms createSite SSRF Enables Arbitrary File Readhttps://feed.craftedsignal.io/briefs/2026-05-haxcms-ssrf/Tue, 19 May 2026 14:44:52 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-05-haxcms-ssrf/HAXcms is vulnerable to Server-Side Request Forgery (SSRF) via the createSite endpoint, allowing an authenticated user to supply arbitrary URLs or local file paths, which are fetched server-side without validation and written to a web-accessible directory, enabling arbitrary file read, internal network access, and cloud credential exposure; this vulnerability is tracked as CVE-2026-46393.HAXcms (v11.0.6) is vulnerable to Server-Side Request Forgery (SSRF) via the createSite endpoint due to insufficient validation of the build.files parameter. An authenticated user can supply arbitrary URLs or local file paths, which are then fetched server-side using file_get_contents() without validation. This allows for reading arbitrary files, accessing internal network services, and potentially exposing cloud credentials through metadata endpoints. This vulnerability was disclosed in GHSA-q862-gcgq-5m6g and is tracked as CVE-2026-46393. Exploitation requires an authenticated session, but default credentials are often present on fresh installs, lowering the barrier to entry.

Attack Chain

  1. Attacker authenticates to the HAXcms application using credentials (default admin/admin may work on fresh installs).
  2. The attacker obtains a valid JWT and CSRF token from the authenticated session.
  3. The attacker crafts a POST request to the /createSite endpoint with a JSON payload.
  4. The payload includes a build.files parameter containing a filename (e.g., poc.txt) as the key and a tmp_name value set to the target URL or file path (e.g., http://169.254.169.254/latest/meta-data/iam/security-credentials/ or /etc/passwd).
  5. The HAXcms server processes the build.files parameter, extracting the tmp_name value without validation.
  6. The server uses file_get_contents() to fetch the content from the URL or file path specified in tmp_name.
  7. The fetched content is saved to the sites/<sitename>/files/<filename> directory.
  8. The attacker retrieves the content by sending a GET request to sites/<sitename>/files/<filename>, thus achieving arbitrary file read or access to internal resources.

Impact

This SSRF vulnerability can be exploited by any authenticated user to access sensitive information. Successful exploitation allows attackers to read arbitrary files from the server’s file system (e.g., /etc/passwd, application configuration files), access internal network services, and potentially expose cloud credentials through metadata endpoints like http://169.254.169.254. This could lead to complete compromise of the server and potentially the associated cloud environment. The affected package npm/@haxtheweb/haxcms-nodejs (vulnerable: <= 25.0.0) means that many instances of HAXcms may be affected.

Recommendation

  • Apply available patches or updates to HAXcms to address CVE-2026-46393.
  • Monitor web server logs for POST requests to /createSite with suspicious URLs or file paths in the build.files parameter, using the Sigma rule Detect HAXcms createSite SSRF Attempt.
  • Inspect network connections originating from the HAXcms server for connections to internal IP addresses or cloud metadata endpoints like 169.254.169.254, as highlighted in the IOC section.
  • Implement strict input validation on the build.files parameter of the /createSite endpoint to prevent arbitrary URL and file path injection.
]]>highadvisoryssrfhaxcmscve-2026-46393vulnerability