Skip to main content
VulnerabilityPublished

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

Affects nukevietSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.2 High : upgrade to 4.5.09 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.5.09
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 to 4.5.09.

Affected software

ProductAffectedFixed in
nukevietnukevietAffected
  • <4.5.09
Fixed in
  • 4.5.09

AI-suggested

Upgrade NukeViet CMS to version 4.5.09 or later, where this vulnerability is fixed. No additional mitigation is required as the fix addresses the root cause by properly escaping output and correcting token validation.

Description

NukeViet CMS is a multi Content Management System. Prior to 4.5.09, the Comment module accepts attacker-controlled base64 content in the status_comment parameter through modules/comment/funcs/main.php; modules/comment/comment.php decodes it with nv_base64_decode() and assigns it to STATUS_COMMENT without output escaping. The required checkss token was derived from the site-wide NV_CACHE_PREFIX rather than NV_CHECK_SESSION, so a token disclosed in public comment markup could be reused across sessions in a crafted URL. An unauthenticated attacker can therefore cause decoded HTML or JavaScript to render in a victim's browser and perform phishing or same-origin actions. This issue is fixed in version 4.5.09.

References

Community reviews

Loading reviews…