CVE-2026-94598: NukeViet CMS: Stored XSS via internal marker injection in iframe srcdoc sanitization

Published Nov 20, 2026
·
Updated

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 NVALLOWEDHTMLTAGS, 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.

Affected Software

1 affected component
NukeViet NukeViet CMS>=4.5.08<4.5.12, <4.6.02

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.5.12
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.6.02

Event History

Nov 20, 2026
CVE Published
via MITRE·07:02 PM
Data Sourced
via MITRE·07:02 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:18 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which installations are affected?

NukeViet versions from 4.5.08 through 4.5.12 and version 4.6.02 are listed as affected. The issue is fixed in versions 4.5.12 and 4.6.02.

2

What does an attacker need to exploit this issue?

An attacker needs a way to submit content that is later viewed, such as a Contact message, an editor-enabled comment, or a submitted article. No authentication is required according to the provided attack vector, but exploitation requires a victim to view the stored content.

3

Are default configurations exposed?

Yes. iframe is enabled by default through NV_ALLOWED_HTML_TAGS, and the vulnerable iframe uses an unsandboxed srcdoc context. This allows injected JavaScript to run with the parent site's origin when the content is viewed.

4

What is the likely impact if exploitation succeeds?

JavaScript can execute in the context of the viewer's session because the unsandboxed srcdoc iframe shares the parent origin. The supplied severity vector indicates high confidentiality impact and low integrity impact.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203