Skip to main content
Menu
CVEs

NukeViet stored XSS in iframe srcdoc sanitization

Affects NukeViet 4.5.08 through 4.6.01 when iframe is in the allowed HTML tags list, including editor input and comments with the editor enabled. Fixed in 4.6.02.

CVE-2026-94598Published , updated

8.2HighCNA
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 that lets a remote attacker, without logging in, plant script in content such as contact messages, comments, or submitted articles. When a viewer opens that content, the script can run with the viewer's session, but the viewer must take an action to trigger it.

Written by a model

Original description

NukeViet CMS is a multi Content Management System. From 4.5.08 until 4.5.12 and 4.6.02, an attacker can place NukeViet's internal {@[, ]@}, [@{, and }@] sanitizer markers in an iframe srcdoc value by encoding square brackets as HTML entities. Recursive NukeViet\Core\Request::filterTags() processing decodes the characters, accepts the forged marker, and later converts it to real markup without normal tag or attribute filtering. Because an unsandboxed srcdoc iframe shares the parent origin and iframe is enabled by default through NV_ALLOWED_HTML_TAGS, stored Contact messages, comments with the editor enabled, or submitted articles can execute JavaScript with the viewer's session. This issue is fixed in versions 4.5.12 and 4.6.02.

Who should check

Teams running NukeViet CMS 4.5.08 to 4.6.01 that allow iframe tags, with editor-enabled comments, contact form messages or news article submissions.

Not fixed by: Workarounds only block new payloads; content stored before remains in the database.

“>= 4.5.08, <= 4.6.01”

github.com

What to do

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

    The iframe tag must be in the allowed HTML tags list (NV_ALLOWED_HTML_TAGS). Input read through the editor (get_editor()) is affected, including comments when the editor is enabled for comments. Affected versions are 4.5.08 up to 4.6.01.
  2. Upgrade to a fixed version: 4.5.12, 4.6.02.

  3. Workaround: Remove iframe from the allowed HTML tags list.

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-94598 (NukeViet CMS: Stored XSS via internal marker injection in iframe srcdoc sanitization), 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-94598 (entry last updated 2026-11-20):
Affected:
- nukeviet nukeviet: from 4.5.08, 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):
- The iframe tag must be in the allowed HTML tags list (NV_ALLOWED_HTML_TAGS). (source: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-p7cw-whjw-crcm)
- Input read through the editor (get_editor()) is affected, including comments when the editor is enabled for comments. (source: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-p7cw-whjw-crcm)
- Affected versions are 4.5.08 up to 4.6.01. (source: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-p7cw-whjw-crcm)
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 iframe from the allowed HTML tags list. (source: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-p7cw-whjw-crcm)
CISA KEV: CVE-2026-94598 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-94598 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-p7cw-whjw-crcm
- https://github.com/nukeviet/nukeviet/commit/13d83ff45072730d10de89195da2154c896d6968
- https://github.com/nukeviet/nukeviet/commit/81a021a6557477efe5a4c713e21b883d138002e6
- 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-94598
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-94598"}.

Affected versions

cve.now Index

20Pof 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
  • Severity8.2/10CVSS 8.2
  • No patch0/5No signal

What would change the score

  • Would score about 70 if added to CISA KEV
  • Would score about 65 if CISA's SSVC rates exploitation active

Timeline

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

Evidence 7

Questions about CVE-2026-94598

Is CVE-2026-94598 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?

A flaw in how NukeViet sanitizes iframe srcdoc content lets an injected internal marker carry a script into stored content. When a viewer loads the page, the script runs in that viewer's origin, where it can read the page and send requests with the viewer's session.

Source: github.com

Which versions are affected by CVE-2026-94598?

nukeviet: from 4.5.08 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.5.08 up to 4.6.01 are affected, but only when iframe is in the allowed HTML tags list (NV_ALLOWED_HTML_TAGS). Input read through the editor (get_editor()) is affected, including comments when the editor is enabled for comments. To check a site, look at the installed version and at whether iframe appears in that allowed tags list.

Source: github.com

How do I fix CVE-2026-94598?

Upgrade to NukeViet 4.6.02, which contains the fix. If you cannot upgrade right away, remove iframe from the allowed HTML tags list.

Source: github.com

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