Skip to main content
Menu
CVEs

NukeViet stored XSS in SVG upload sanitizer

Affects NukeViet 4.6.01 and earlier and 4.5.11 and earlier on sites that accept SVG uploads. Fixed in 4.5.12 and 4.6.02.

CVE-2026-94567Published , updated

9.3CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 4.5.12, 4.6.02
Who is exposed
Specific setups only

Summary

NukeViet CMS has a stored cross-site scripting flaw in its SVG upload handling: a script hidden in an uploaded file is saved to the server and can run in a viewer's browser. An attacker can reach it remotely without logging in, but a user must take an action before the script runs.

Written by a model

Original description

NukeViet CMS is a multi Content Management System. Prior to 4.5.12 and 4.6.02, an attacker with access to an SVG upload flow can hide a script element in an internal DTD entity. NukeViet\Files\Upload::check_svg_tmpfile() loads the document without entity expansion, leaving a DOMEntityReference, and sanitize_svg_dom() inspects only element nodes, while browsers expand the entity when the stored file is served as image/svg+xml. The SVG path also returned before verify_image() and preserved the original bytes, so the hidden script reached disk unchanged. Guest comment attachments make the upload unauthenticated only when a module's comment feature is open to the All or Guest group and allowattachcomm is enabled; module administrators can also use the file manager, allowing same-origin script execution in an administrator's session. This issue is fixed in versions 4.5.12 and 4.6.02.

Who should check

Teams running NukeViet CMS 4.6.01 or earlier or 4.5.11 or earlier, including sites that vendor the vinades/nukeviet Composer package and sites that accept SVG uploads

Not fixed by: Updating only the CMS tree does not fix sites that vendor the vinades/nukeviet package.

“<=4.6.01, <=4.5.11”

github.com

What to do

  1. Check whether your setup matches what the bug needs.

    Site runs an affected NukeViet version (4.6.01 or earlier, or 4.5.11 or earlier) and accepts SVG uploads. Guest-attachment path needs a module comment feature opened to the public group. Guest-attachment path needs comment attachments enabled.
  2. Upgrade to a fixed version: 4.5.12, 4.6.02.

  3. Workaround: Remove svg from the allowed upload types in the admin upload configuration and in the extension groups used by comment attachments and banner plans.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-94567 (NukeViet CMS: Stored XSS via SVG upload: the sanitizer is blind to markup hidden inside an internal DTD entity), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-94567 (entry last updated 2026-11-20):
Affected:
- nukeviet nukeviet: fixed in 4.5.12; from 4.6.00, fixed in 4.6.02
Fixed versions: 4.5.12, 4.6.02.
Conditions (all must be true for the bug to be hit):
- Site runs an affected NukeViet version (4.6.01 or earlier, or 4.5.11 or earlier) and accepts SVG uploads. (source: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-cp55-wmv6-wxpp)
- Guest-attachment path needs a module comment feature opened to the public group. (source: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-cp55-wmv6-wxpp)
- Guest-attachment path needs comment attachments enabled. (source: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-cp55-wmv6-wxpp)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, a user action.
Workaround: Remove svg from the allowed upload types in the admin upload configuration and in the extension groups used by comment attachments and banner plans. (source: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-cp55-wmv6-wxpp)
CISA KEV: CVE-2026-94567 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-94567 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/nukeviet/nukeviet/security/advisories/GHSA-cp55-wmv6-wxpp
- https://github.com/nukeviet/nukeviet/commit/912823e2581afc23dc39dabdb7d94c718efc78f6
- https://github.com/nukeviet/nukeviet/commit/b4abcddd3a3a628e251d88571f3968822fab4406
- https://github.com/nukeviet/nukeviet/blob/4.5.13/CHANGELOG.txt
- https://github.com/nukeviet/nukeviet/releases/tag/4.6.02
- https://nukeviet.vn/vi/news/Tin-tuc/thong-bao-phat-hanh-nukeviet-4-6-02-858.html
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-94567
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-94567"}.

Affected versions

cve.now Index

21Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure12/25Specific setups only, reachable over the network without a login
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.3/10CVSS 9.3
  • No patch0/5No signal

What would change the score

  • Would score about 71 if added to CISA KEV
  • Would score about 66 if CISA's SSVC rates exploitation active

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 7

Questions about CVE-2026-94567

Is CVE-2026-94567 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

The SVG upload sanitizer misses markup hidden inside an internal DTD entity, so a stored file can carry a script. When the file URL is opened in a browser, the script runs in the site's own origin, and a module admin can use the file manager to reach site-admin privileges.

Source: github.com

Which versions are affected by CVE-2026-94567?

nukeviet: before 4.5.12; from 4.6.00 before 4.6.02.

Source: cve.now feed data

Am I affected, and how do I check?

Versions 4.6.01 and earlier, and 4.5.11 and earlier, are affected when the site accepts SVG uploads. Check the installed version in the admin panel and whether svg is among the allowed upload types in the admin upload configuration.

Source: github.com

How do I fix CVE-2026-94567?

Upgrade to 4.5.12 on the 4.5 line or to 4.6.02 on the 4.6 line.

Source: github.com

No corrections so far. Something wrong on this page? Report an error.