Skip to main content
Menu
CVEs

NukeViet unauthenticated SSRF via forwarded host header handling

Affects NukeViet versions before 4.5.09 when a POST containing __serverInfoUpdate=1 is handled before authentication and the forwarded host is not checked against my_domains. Fixed in 4.5.09.

CVE-2026-55372Published , updated

7.2HighCNA
Exploited
No known exploitation
Fix
Fixed in 4.5.09
Who is exposed
Not reported

Summary

Attackers can reach NukeViet CMS remotely and without logging in, by sending a crafted request that spoofs forwarded host headers. This lets them make the server send blind, HEAD-only requests to internal hosts and ports, which can reveal internal network details and poison cached server headers.

Written by a model

Original description

NukeViet CMS is a multi Content Management System. Prior to 4.5.09, an unauthenticated attacker can submit the __serverInfoUpdate=1 field while controlling X-Forwarded-Host and X-Forwarded-Proto. NukeViet\Core\Server::standardizeHost() did not validate the forwarded host against my_domains, and a trailing slash could preserve an attacker-selected port that server_info_update() used to construct a cURL request in includes/ini.php before authentication. The blind, HEAD-only request uses a fixed path, but it permits internal host and port discovery and can poison cached server_headers. This issue is fixed in version 4.5.09.

Who should check

Teams running NukeViet CMS 4.5.08 or earlier (nukeviet/nukeviet via Composer) on internet-facing sites.

“nukeviet/nukeviet”

github.com

What to do

  1. Upgrade to a fixed version: 4.5.09.

  2. Workaround: Configure the reverse proxy / web server to strip or override client-supplied X-Forwarded-Host, X-Forwarded-Proto, and X-Forwarded-Port headers, and ensure my_domains is configured with the site's canonical domain(s).

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-55372 (NukeViet CMS: Pre-authentication SSRF via X-Forwarded-Host in NukeViet), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-55372 (entry last updated 2026-11-20):
Affected:
- nukeviet nukeviet: fixed in 4.5.09
Fixed versions: 4.5.09.
Conditions (all must be true for the bug to be hit):
- The request must be a POST carrying the __serverInfoUpdate=1 field, which is handled before authentication. (source: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-4chg-4752-w88r)
- The forwarded host is not checked against the site's configured domains (my_domains). (source: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-4chg-4752-w88r)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
Workaround: Configure the reverse proxy / web server to strip or override client-supplied X-Forwarded-Host, X-Forwarded-Proto, and X-Forwarded-Port headers, and ensure my_domains is configured with the site's canonical domain(s). (source: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-4chg-4752-w88r)
CISA KEV: CVE-2026-55372 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-55372 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/nukeviet/nukeviet/security/advisories/GHSA-4chg-4752-w88r
- https://github.com/nukeviet/nukeviet/commit/a16d6dc9891fb38d5ad16b64e0303910adf94c01
- https://github.com/nukeviet/nukeviet/commit/f0e06cd543feff7d21f683a9be9b0b06e7192bf3
- https://github.com/nukeviet/nukeviet/releases/tag/4.5.09
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-55372
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-55372"}.

Affected versions

cve.now Index

24Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.2/10CVSS 7.2
  • No patch0/5No signal

What would change the score

  • Would score about 69 if added to CISA KEV
  • Would score about 64 if CISA's SSVC rates exploitation active
  • Would score about 29 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 5

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · nukeviet/nukeviet · Advisory GHSA-4chg-4752-w88r
CVE record 1Establishes: The identifier and description.
RecordCVE List · CVE-2026-55372
Other links 3
RepositoryGitHub · nukeviet/nukeviet · Commit a16d6dc9
RepositoryGitHub · nukeviet/nukeviet · Commit f0e06cd5
RepositoryGitHub · nukeviet/nukeviet · Release 4.5.09

Questions about CVE-2026-55372

Is CVE-2026-55372 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

An unauthenticated POST with the __serverInfoUpdate=1 field can make the server send blind, HEAD-only requests to attacker-chosen hosts and ports, which allows internal host and port discovery and poisoning of the cached server_headers.

Source: github.com

Which versions are affected by CVE-2026-55372?

nukeviet: before 4.5.09.

Source: cve.now feed data

Am I affected, and how do I check?

The issue applies to NukeViet versions before 4.5.09, where the X-Forwarded-Host value is not validated against the site's configured domains (my_domains). To check, look at the installed NukeViet version and at the my_domains setting in the site configuration.

Source: github.com

How do I fix CVE-2026-55372?

Upgrade to NukeViet 4.5.09, which fixes this issue. If an upgrade is not possible yet, configure the reverse proxy or web server to strip or override client-supplied X-Forwarded-Host, X-Forwarded-Proto, and X-Forwarded-Port headers, and make sure my_domains lists the site's canonical domain(s).

Source: github.com

No corrections so far. Something wrong on this page? Report an error.