CVE-2026-94562: NukeViet CMS: Remote Code Execution via unrestricted custom field validation callback in the `users` module
NukeViet CMS is a multi Content Management System. Prior to 4.6.01, a super-administrator satisfying the NVISSPADMIN gate can use modules/users/admin/fields.php to store an arbitrary existing PHP function in the funccallback setting for a custom profile field because the callback name is checked only with functionexists() and no allowlist restricts which function may be selected. modules/users/fields.check.php later invokes that function through calluserfunc() 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.
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 4.6.01 - Operational
After upgrading, manually clean malicious callbacks already stored in the database, including the affected custom field's func_callback setting.
Event History
Frequently Asked Questions
Who can configure the malicious callback, and who can trigger it?
Only a super-administrator that satisfies the NV_IS_SPADMIN gate can store an arbitrary existing PHP function as a custom field callback. After it is configured, ordinary users can trigger the callback through registration or profile editing; administrators can also trigger it while editing profiles.
What access does an attacker need to achieve operating-system command execution?
The attacker needs super-administrator access to configure a custom profile field with a command-execution PHP function. The resulting commands run as the web-server account, not necessarily as the super-administrator's operating-system user.
Are default installations affected without prior administrative configuration?
Exploitation requires a super-administrator to first write a malicious func_callback value for a custom profile field. The described trigger paths invoke a stored callback, so the operating-system execution condition depends on that malicious configuration being present.
Does upgrading to 4.6.01 remove an already configured malicious callback?
No. The fix validates callbacks when they are written, but it does not remove malicious callback values already stored in the database; those entries must be identified and cleaned manually.
How can I determine whether the instance may already be affected?
Review stored custom profile field func_callback settings for arbitrary or command-execution PHP functions, particularly in the users module's custom field configuration. Any suspicious existing callback should be removed manually even after upgrading to 4.6.01.