Skip to main content
Menu
CVEs

NukeViet stored XSS in comment reply display names

NukeViet 4.x through 4.5.08 is affected through comment Reply links that show a poster's display name. Fixed in 4.5.09.

CVE-2026-49259Published , updated

8.7HighCNA
Exploited
No known exploitation
Fix
Fixed in 4.5.09
Who is exposed
Specific setups only

Summary

NukeViet CMS has a stored cross-site scripting flaw in its comment reply links. A remote attacker with a low-privileged account can place script-breaking text in their first and last name profile fields, which are used as the comment display name. When a visitor clicks Reply on a comment, the attacker's JavaScript runs in that visitor's browser, including an administrator's session.

Written by a model

Original description

NukeViet CMS is a multi Content Management System. From the 4.x release line until 4.5.09, a low-privileged authenticated user can store script-breaking content in the first_name and last_name profile fields used to form a comment display name. Both reply links in themes/default/modules/comment/comment.tpl interpolate {COMMENT.post_name} into the inline onclick call to nv_commment_feedback(). HTML numeric references produced by Request::_get_title() are decoded by the browser before JavaScript parsing, so clicking Reply can terminate the string and execute attacker-controlled JavaScript in the visitor's origin, including an administrator's session. This issue is fixed in version 4.5.09.

Who should check

Teams running NukeViet 4.x through 4.5.08 with comments enabled, including anyone using the default theme comment template.

Not fixed by: HTML entity encoding alone does not fix this bug.

“A stored cross-site scripting (XSS) vulnerability exists in NukeViet CMS versions 4.x through 4.5.08.”

github.com

What to do

  1. Check whether your setup matches what the bug needs.

    NukeViet 4.x up to and including 4.5.08. Comment templates with the Reply link rendering the poster's display name in the inline onclick handler. A victim must click the Reply link on a comment posted by the attacker's account.
  2. Upgrade to a fixed version: 4.5.09.

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-49259 (NukeViet: stored XSS through comment reply display names), 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-49259 (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):
- NukeViet 4.x up to and including 4.5.08. (source: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-w2w5-w2pw-r929)
- Comment templates with the Reply link rendering the poster's display name in the inline onclick handler. (source: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-w2w5-w2pw-r929)
- A victim must click the Reply link on a comment posted by the attacker's account. (source: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-w2w5-w2pw-r929)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, a user action.
CISA KEV: CVE-2026-49259 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-49259 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-w2w5-w2pw-r929
- https://github.com/nukeviet/nukeviet/commit/8dfad9d4d3e44b970a7816f60705235e6c0ee604
- 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-49259
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-49259"}.

Affected versions

cve.now Index

17Pof 100 · provisional · methodology v3
  • 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

  1. CVE published
  2. First seen by cve.now

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · nukeviet/nukeviet · Advisory GHSA-w2w5-w2pw-r929
CVE record 1Establishes: The identifier and description.
RecordCVE List · CVE-2026-49259
Other links 2
RepositoryGitHub · nukeviet/nukeviet · Commit 8dfad9d4
RepositoryGitHub · nukeviet/nukeviet · Release 4.5.09

Questions about CVE-2026-49259

Is CVE-2026-49259 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?

A user with a regular account can make JavaScript run in the browser of any visitor who clicks Reply on that user's comment, including site administrators.

Source: github.com

Which versions are affected by CVE-2026-49259?

nukeviet: before 4.5.09.

Source: cve.now feed data

Am I affected, and how do I check?

NukeViet 4.x versions up to and including 4.5.08 are affected. The flaw is in the default comment template, themes/default/modules/comment/comment.tpl at line 27, where top-level comments put the poster's display name into the inline onclick handler of the Reply link. The file can be checked in the installed theme folder.

Source: github.com

How do I fix CVE-2026-49259?

Upgrade to NukeViet 4.5.09, which is the fixed version.

Source: github.com

No corrections so far. Something wrong on this page? Report an error.