Skip to main content
VulnerabilityPublished

CVE-2026-94562: nukeviet · Code Injection

Affects nukevietSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.2 High : upgrade to 4.6.01 soon.

Data as of 20 Nov 2026, 19:14 UTC

CVSS 3.1 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.17.2
Patch
Available – fixed in 4.6.01
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade nukeviet and nukeviet/nukeviet to 4.6.01.

Affected software

ProductAffectedFixed in
nukevietnukevietAffected
  • <4.6.01
Fixed in
  • 4.6.01
GitHubnukeviet/nukevietpkg:github/nukeviet/nukevietOther threatsAffected
  • <4.6.01
Fixed in
  • 4.6.01

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade NukeViet CMS to version 4.6.01 or later, where this vulnerability is fixed. Note that upgrading does not remove any malicious callbacks already stored in the database; these must be identified and cleaned manually to fully remediate the issue.

Description

NukeViet CMS versions prior to 4.6.01 contain a code injection vulnerability that allows a super-administrator to store an arbitrary PHP function name in a custom profile field's callback setting without proper restriction. This function is later invoked during user registration or profile editing, potentially enabling command execution as the web server user. The vulnerability is fixed in version 4.6.01, but existing malicious callbacks stored before upgrading must be manually removed.

References

Community reviews

Loading reviews…