Skip to main content
Menu
CVEs

NukeViet login lockout bypass via spoofed forwarded-IP headers

CVE-2026-94566Published , updated

5.3MediumCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 4.6.01
Who is exposed
Not reported

Summary

NukeViet CMS trusts forwarded client-IP headers without first checking that the request comes from a trusted proxy. A remote attacker, without logging in or any user action, can change the X-Forwarded-For value to bypass the administrator login lockout, which allows effectively unlimited password guessing.

Written by a model

Original description

NukeViet CMS is a multi Content Management System. In 4.6.00, an unauthenticated attacker can rotate X-Forwarded-For because vendor/vinades/nukeviet/Core/Ips.php accepts forwarded client-IP headers without first confirming that REMOTE_ADDR is a trusted proxy. The resulting NV_CLIENT_IP keys the administrator login blocker in includes/core/admin_login.php; changing only the header value bypasses that lockout and permits effectively unlimited password guesses. The same spoofable address is also consumed by the user login blocker in modules/users/funcs/login.php, IP restrictions, bans, flood controls, and security logs, but those additional code-level effects were not dynamically demonstrated. This issue is fixed in version 4.6.01.

What to do

Upgrade to a fixed version: 4.6.01.

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-94566 (NukeVie: Login Lockout Bypass via Untrusted Forwarded-IP Headers), 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-94566 (entry last updated 2026-11-20):
Affected:
- nukeviet nukeviet: from 4.6.00, fixed in 4.6.01
Fixed versions: 4.6.01.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-94566 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-94566 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-ccf2-6mf6-j78j
- https://github.com/nukeviet/nukeviet/commit/aee1a6d1ab6b0c41f9ae80fb3cc76c5b49562a22
- https://github.com/nukeviet/nukeviet/releases/tag/4.6.01
- https://nukeviet.vn/vi/news/Tin-tuc/thong-bao-phat-hanh-nukeviet-4-6-01-857.html
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-94566
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-94566"}.

Affected versions

cve.now Index

40Pof 100 · provisional · methodology v3
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.3/10CVSS 5.3
  • No patch0/5No signal

What would change the score

  • Would score about 70 if added to CISA KEV
  • Would score about 65 if CISA's SSVC rates exploitation active
  • Would score about 45 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: yes · Technical impact: partial

  4. Record last updated

Evidence 6

Questions about CVE-2026-94566

Is CVE-2026-94566 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. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-94566?

nukeviet: from 4.6.00 before 4.6.01.

Source: cve.now feed data

How do I fix CVE-2026-94566?

Upgrade to a fixed version: 4.6.01.

Source: cve.now feed data

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