NukeViet unauthenticated stored XSS in contact module
- Exploited
- No known exploitation
- Fix
- Fixed in 4.6.01
- Who is exposed
- Not reported
Summary
NukeViet CMS's Contact module has a stored cross-site scripting flaw that lets a remote visitor, without logging in, submit a message that runs script when staff view it in the administration area. The script can perform actions on behalf of the logged-in staff member but cannot directly read their HttpOnly session cookie.
Written by a model
Original description
NukeViet CMS is a multi Content Management System. Prior to 4.6.01, an unauthenticated visitor can submit Contact module content containing numeric HTML entities with more than eight leading zeros in a URL-bearing attribute. NukeViet\Core\Request::unhtmlentities() does not decode that form before filterAttr() checks for a javascript: scheme, but browsers decode it when rendering the stored content. With an allowed tag such as the default iframe, the reconstructed script URL executes in the administration origin when staff view the message, permitting session-riding actions while remaining unable to read the HttpOnly session cookie directly. This issue is fixed in version 4.6.01.
What to do
Upgrade to a fixed version: 4.6.01.
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-94564 (NukeViet CMS: Unauthenticated Stored XSS in the Contact module via HTML sanitizer bypass), 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-94564 (entry last updated 2026-11-20):
Affected:
- nukeviet nukeviet: fixed in 4.6.01
Fixed versions: 4.6.01.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-94564 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-94564 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-7pv3-g7fw-7xhq
- https://github.com/nukeviet/nukeviet/commit/e2441029b158b67cf396990230276ec67e05e2be
- https://github.com/nukeviet/nukeviet/releases/tag/4.6.01
- https://nukeviet.vn/vi/news/Tin-tuc/thong-bao-phat-hanh-nukeviet-4-6-01-857.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-94564
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-94564"}.Affected versions
- nukeviet nukevietfixed in 4.6.01
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- 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
- Would score about 30 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 5
| Kind | Source |
|---|---|
| Vendor advisory 2Establishes: Affected and fixed versions. | |
| Advisory | GitHub · nukeviet/nukeviet · Advisory GHSA-7pv3-g7fw-7xhq |
| Link | nukeviet.vn · vi/news/Tin-tuc/thong-bao-phat-hanh-nukeviet-4-6-01-857.html |
| CVE record 1Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-94564 |
| Other links 2 | |
| Repository | GitHub · nukeviet/nukeviet · Commit e2441029 |
| Repository | GitHub · nukeviet/nukeviet · Release 4.6.01 |
Questions about CVE-2026-94564
Is CVE-2026-94564 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
Which versions are affected by CVE-2026-94564?
nukeviet: before 4.6.01.
Source: cve.now feed data
How do I fix CVE-2026-94564?
Upgrade to a fixed version: 4.6.01.
Source: cve.now feed data
Related
- CVE-2026-94565NukeViet CMS: Unauthenticated Stored XSS in the Contact module
- CVE-2026-54064NukeViet CMS: Multiple Anti-XSS Filter Bypasses Leading to Stored XSS in News 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-48118NukeViet CMS: Unauthenticated Reflected XSS in Comment Module
No corrections so far. Something wrong on this page? Report an error.