Skip to main content
VulnerabilityPublished

CVE-2026-94564: nukeviet · Cross-site Scripting

Affects nukevietSource CVE Database V5

0
Compare

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

Data as of 20 Nov 2026, 19:29 UTC

CVSS 3.1 base score
8.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.18.2
Patch
Available – fixed in 4.6.01
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N

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. No other mitigation is required as the vendor has provided an official fix.

Description

NukeViet CMS is a multi Content Management System. Prior to 4.6.01, an unauthenticated visitor can submit Contact module content containing numeric HTML entities with more than eight leading zeros in a URL-bearing attribute. NukeViet\Core\Request::unhtmlentities() does not decode that form before filterAttr() checks for a javascript: scheme, but browsers decode it when rendering the stored content. With an allowed tag such as the default iframe, the reconstructed script URL executes in the administration origin when staff view the message, permitting session-riding actions while remaining unable to read the HttpOnly session cookie directly. This issue is fixed in version 4.6.01.

References

Community reviews

Loading reviews…