Is CVE-2026-49259 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-49259 being exploited in the wild.

How severe is CVE-2026-49259?

High severity, with a CVSS score of 8.7, published 13 July 2026.

Which products and versions are affected?

NukeViet 4.x through 4.5.08; nukeviet/nukeviet (Packagist) < 4.5.09, ECOSYSTEM:introduced=0,fixed=4.6.00.

Is there a fix for CVE-2026-49259?

Yes. nukeviet/nukeviet (Packagist): upgrade to 4.6.00 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-49259 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-49259?

Check whether you run NukeViet or nukeviet/nukeviet (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-49259: NukeViet CMS stored XSS in comment reply component

Q: Is there a fix for CVE-2026-49259?

Yes. nukeviet/nukeviet (Packagist): upgrade to 4.6.00 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-49259 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-49259?

Check whether you run NukeViet or nukeviet/nukeviet (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-49259 · Severity: high · CVSS 8.7 · Published 2026-07-13

A security vulnerability in NukeViet CMS allows users to inject malicious scripts into their profile names. When other users or administrators interact with comments made by the attacker, these scripts execute in their browser. This can lead to unauthorized administrative actions, theft of sensitive information, or account takeover.

Technologies: NukeViet, nukeviet/nukeviet (Packagist). Vendors: NukeViet, Packagist.

Quick answers

Is CVE-2026-49259 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-49259 being exploited in the wild.
How severe is CVE-2026-49259?: High severity, with a CVSS score of 8.7, published 13 July 2026.
Which products and versions are affected?: NukeViet 4.x through 4.5.08; nukeviet/nukeviet (Packagist) < 4.5.09, ECOSYSTEM:introduced=0,fixed=4.6.00.
Is there a fix for CVE-2026-49259?: Yes. nukeviet/nukeviet (Packagist): upgrade to 4.6.00 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-49259 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-49259?: Check whether you run NukeViet or nukeviet/nukeviet (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

nukeviet/nukeviet (Packagist): upgrade to 4.6.00 or later
```
composer require nukeviet/nukeviet:^4.6.00
```

Technical details

A stored cross-site scripting (XSS) vulnerability exists in NukeViet CMS versions 4.x through 4.5.08 due to improper output encoding of the {COMMENT.post_name} template variable. While the system uses HTML entity encoding for profile fields, it fails to apply JavaScript-context escaping when these fields are interpolated into inline 'onclick' handlers in 'themes/default/modules/comment/comment.tpl'. An attacker can provide a crafted display name that breaks out of the JavaScript string literal after the browser decodes the HTML entities. This allows for arbitrary script execution when a victim clicks the 'Reply' link on the attacker's comment. The vulnerability is patched in version 4.6.00.

Affected products

NukeViet NukeViet CMS 4.x through 4.5.08

Identifiers

CVE-2026-49259
GHSA-w2w5-w2pw-r929

Timeline

2026-07-13: advisory: GHSA-w2w5-w2pw-r929 published
2026-07-13: disclosed
2026-07-13: patched: Fix released in version 4.6.00

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.