Skip to main content
Menu
CVEs

NukeViet remote code execution in users module field validation

CVE-2026-94562Published , updated

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

Summary

NukeViet CMS's users module lets a super-administrator store any existing PHP function as the validation callback for a custom profile field, and that function runs whenever the field is validated. An attacker who can reach the site over the network and already holds super-administrator access could use this to run operating-system commands as the web-server account.

Written by a model

Original description

NukeViet CMS is a multi Content Management System. Prior to 4.6.01, a super-administrator satisfying the NV_IS_SPADMIN gate can use modules/users/admin/fields.php to store an arbitrary existing PHP function in the func_callback setting for a custom profile field because the callback name is checked only with function_exists() and no allowlist restricts which function may be selected. modules/users/fields.check.php later invokes that function through call_user_func() when the field is validated through registration, profile editing, or administrator editing. Selecting a command-execution function crosses the super-administrator to operating-system boundary and executes commands as the web-server account, while ordinary users can trigger the stored callback after it is configured. Because the remediation validates callbacks only when they are written, upgrading does not remove a malicious callback already stored in the database, which must be cleaned manually. 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-94562 (NukeViet CMS: Remote Code Execution via unrestricted custom field validation callback in the `users` module), 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-94562 (entry last updated 2026-11-20):
Affected:
- nukeviet nukeviet: 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-94562 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-94562 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-hjxg-4v29-j33c
- https://github.com/nukeviet/nukeviet/commit/1aa773c7feb41ffe95b53501df5a6956002ca61b
- 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-94562
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-94562"}.

Affected versions

cve.now Index

10Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • 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 65 if added to CISA KEV
  • Would score about 60 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 2Establishes: Affected and fixed versions.
AdvisoryGitHub · nukeviet/nukeviet · Advisory GHSA-hjxg-4v29-j33c
Linknukeviet.vn · vi/news/Tin-tuc/thong-bao-phat-hanh-nukeviet-4-6-01-857.html
CVE record 1Establishes: The identifier and description.
RecordCVE List · CVE-2026-94562
Other links 2
RepositoryGitHub · nukeviet/nukeviet · Commit 1aa773c7
RepositoryGitHub · nukeviet/nukeviet · Release 4.6.01

Questions about CVE-2026-94562

Is CVE-2026-94562 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

Which versions are affected by CVE-2026-94562?

nukeviet: before 4.6.01.

Source: cve.now feed data

How do I fix CVE-2026-94562?

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.