Skip to main content
VulnerabilityPublished

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

Affects nukevietSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.3 Critical : upgrade to 4.6.01 as a priority.

Data as of 20 Nov 2026, 19:29 UTC

CVSS 3.1 base score
9.3Critical
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.19.3
Patch
Available – fixed in 4.6.01
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/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
  • >=3.0.0 <4.6.01
Fixed in
  • 4.6.01
GitHubnukeviet/nukevietpkg:github/nukeviet/nukevietOther threatsAffected
  • >=3.0.0 <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 mitigations are indicated or recommended by the vendor advisory.

Description

NukeViet CMS is a multi Content Management System. From the 3.x release line until 4.6.01, an unauthenticated visitor can submit a Contact module message containing an event-handler attribute prefixed by a slash. NukeViet\Core\Request::filterTags() tokenizes attributes using only ASCII spaces, so it sees /onerror and misses the ^on denylist, while the browser treats the slash as a separator and activates onerror. The message is stored and rendered without output encoding in the administration panel, which lacks a Content Security Policy, allowing same-origin JavaScript execution when an administrator opens the message. This issue is fixed in version 4.6.01.

References

Community reviews

Loading reviews…