NukeViet: Multiple Anti-XSS Filter Bypasses Leading to Stored XSS in News Module

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.7 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary Two filter-bypass techniques in NukeViet\Core\Request::filterAttr() and NukeViet\Core\Request::unhtmlentities() allow a low-privileged user (any account with news post permission) to store and serve arbitrary JavaScript to any visitor of the affected page. Affected Component vendor/vinades/nukeviet/Core/Request.php — class NukeViet\Core\Request Vulnerability Details Bypass 1 — Form Feed character prefix (\x0C) before event handler name The filterAttr() method blocks event-handler attributes using: PHP's trim() does not strip the ASCII Form Feed character (\x0C, U+000C). An attacker can prefix the attribute name with \x0C so that \x0Conerror does not match /^on/. The HTML5 browser parser treats \x0C as a valid whitespace separator and correctly activates the event handler. Proof-of-concept payload (URL-encoded POST body field bodyhtml): Bypass 2 — Decimal HTML entity tab (	) inside javascript: URI unhtmlentities() strips the hex-encoded tab 	 via strireplace, but did…

Published by the source

13 Jul 2026, 17:54 UTC

Last modified by the source

13 Jul 2026, 17:54 UTC

Source last checked

26 Oct 2026, 14:50 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-465g-4q99-5x86

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-54064

Advisory: NukeViet: Multiple Anti-XSS Filter Bypasses Leading to Stored XSS in News Module
IDs: CVE-2026-54064, GHSA-465g-4q99-5x86
Record: https://patchnext.com/advisories/cve-2026-54064 (revision 1, source checked 26 Oct 2026, 14:50 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: nukeviet/nukeviet 4.6.00. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist nukeviet/nukeviet: affected < 4.6.00; fixed in 4.6.00

## Suggested inspection (read-only)
- Packagist nukeviet/nukeviet: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on nukeviet/nukeviet.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-465g-4q99-5x86 (GitHub-reviewed advisory GHSA-465g-4q99-5x86 lists affected ranges: Packagist nukeviet/nukeviet >=0 <4.6.00)

Commands are suggestions: review each one before running it.