NukeViet stored XSS via filter bypasses in news module
Affects NukeViet CMS accounts with news-posting permission on the news module, in versions before 4.5.09. Fixed in 4.5.09.
- Exploited
- No known exploitation
- Fix
- Fixed in 4.5.09
- Who is exposed
- Specific setups only
Summary
NukeViet CMS's news module contains multiple filter bypasses that let a remote attacker store a cross-site scripting payload that runs in visitors' browsers, including administrators' browsers. The attacker needs to log in with news-posting permission, and the script runs when a visitor opens the affected page.
Written by a model
Original description
NukeViet CMS is a multi Content Management System. Prior to 4.5.09, a user with news-posting permission can bypass NukeViet\Core\Request::filterAttr() by prefixing an event-handler attribute with an ASCII form-feed character, which PHP trimming preserves but browsers treat as whitespace. NukeViet\Core\Request::unhtmlentities() omitted a decimal HTML entity tab embedded in a javascript: URI. These parser differences allow persistent event handlers or script URLs to survive filtering in vendor/vinades/nukeviet/Core/Request.php and execute for visitors, including administrators. This issue is fixed in version 4.5.09.
What to do
Check whether your setup matches what the bug needs.
Attacker holds a news-posting permission on the news moduleUpgrade to a fixed version: 4.5.09.
Workaround: None; update to the patched version.
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-54064 (NukeViet CMS: Multiple Anti-XSS Filter Bypasses Leading to Stored XSS in News Module), 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-54064 (entry last updated 2026-11-20):
Affected:
- nukeviet nukeviet: fixed in 4.5.09
Fixed versions: 4.5.09.
Conditions (all must be true for the bug to be hit):
- Attacker holds a news-posting permission on the news module (source: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-465g-4q99-5x86)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, a user action.
Workaround: None; update to the patched version. (source: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-465g-4q99-5x86)
CISA KEV: CVE-2026-54064 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-54064 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-465g-4q99-5x86
- https://github.com/nukeviet/nukeviet/commit/4f3f6dbd724a28a1c455c009b2d59f9d8bc95d48
- https://github.com/nukeviet/nukeviet/commit/ab804d4c95d581c76d8f69675d45edbc313fe734
- https://github.com/nukeviet/nukeviet/releases/tag/4.5.09
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-54064
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-54064"}.Affected versions
- nukeviet nukevietfixed in 4.5.09
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
Evidence 5
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · nukeviet/nukeviet · Advisory GHSA-465g-4q99-5x86 |
| CVE record 1Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-54064 |
| Other links 3 | |
| Repository | GitHub · nukeviet/nukeviet · Commit 4f3f6dbd |
| Repository | GitHub · nukeviet/nukeviet · Commit ab804d4c |
| Repository | GitHub · nukeviet/nukeviet · Release 4.5.09 |
Questions about CVE-2026-54064
Is CVE-2026-54064 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?
Anti-XSS filters in the NukeViet news module can be bypassed, so a user with news-posting permission can store JavaScript that runs in the browser of any visitor, including administrators. This can enable session cookie theft, credential harvesting, defacement, and further privilege escalation.
Source: github.com
Which versions are affected by CVE-2026-54064?
nukeviet: before 4.5.09.
Source: cve.now feed data
Am I affected, and how do I check?
The affected product is NukeViet CMS before 4.5.09, and the risk applies where an account holds news-posting permission on the news module. To check a site, look at the installed NukeViet version and confirm which accounts have news post permission.
Source: github.com
How do I fix CVE-2026-54064?
Update NukeViet to version 4.5.09 or later, which is the fixed version named by the advisory. The advisory gives no workaround other than updating to the patched version.
Source: github.com
Related
- CVE-2026-94567NukeViet CMS: Stored XSS via SVG upload: the sanitizer is blind to markup hidden inside an internal DTD entity
- CVE-2026-94565NukeViet CMS: Unauthenticated Stored XSS in the Contact module
- CVE-2026-54065NukeViet CMS: Path Traversal to Arbitrary File Deletion in Edit Comment Function
- CVE-2026-49259NukeViet: stored XSS through comment reply display names
- CVE-2026-41147NukeViet CMS: Stored Cross-Site Scripting (XSS) via insufficient server-side input sanitization in Request class
- CVE-2026-94598NukeViet CMS: Stored XSS via internal marker injection in iframe srcdoc sanitization
No corrections so far. Something wrong on this page? Report an error.