VulnerabilityPublished 13 Jul 2026

CVE-2026-48118: NukeViet · Unauthenticated Reflected XSS in Comment Module

Affects nukeviet/nukevietSource GCVE Database

Compare

Not known to be exploited · CVSS 8.2 High : upgrade to 4.6.00 soon.

Data as of 14 Jul 2026, 10:01 UTC

CVSS 3.1 base score

8.2High

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 4.6.00

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Changed
Confidentiality: High
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade nukeviet/nukeviet to 4.6.00.

Affected software

Product	Affected	Fixed in
Packagistnukeviet/nukeviet	Affected <4.6.00	Fixed in 4.6.00

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available that addresses both root causes: the checkss token is now bound to the user session by replacing the static NV_CACHE_PREFIX with NV_CHECK_SESSION, and the status_comment parameter handling has been corrected to properly sanitize decoded content before rendering. Users should upgrade to NukeViet version 4.6.00 or later. Until patched, avoid exposing the comment module with untrusted input in URLs and consider implementing additional input validation or Content Security Policy restrictions to mitigate exploitation.

Description

NukeViet versions prior to 4.6.00 contain a reflected cross-site scripting (XSS) vulnerability in the Comment module via the status_comment URL parameter. The parameter accepts base64-encoded HTML/JavaScript that is decoded server-side and rendered without escaping, allowing arbitrary script execution. Additionally, the anti-forgery token checkss is derived from a static site-wide value rather than a per-session value, making it reusable across users and enabling exploitation via crafted URLs without authentication. This vulnerability allows attackers to execute malicious scripts in victims' browsers within the site's origin, potentially capturing sensitive information such as credentials. The vulnerability has a high severity rating with a CVSS 3.1 base score of 8.2.

Impact

Successful exploitation allows attackers to execute arbitrary JavaScript in the context of the victim's browser session on the vulnerable site. This can lead to theft of sensitive information such as credentials, session tokens, and other data accessible to scripts running in the site's origin. The vulnerability requires the victim to open a crafted URL but does not require authentication. The integrity of the victim's session can be compromised by DOM manipulation and unauthorized authenticated requests. There is no impact on availability. The vulnerability has a high confidentiality impact and low integrity impact.

Summary

The vulnerability consists of two main flaws in NukeViet's Comment module. First, the status_comment parameter is filtered before base64 decoding, allowing attacker-controlled HTML/JavaScript to bypass sanitization and be rendered unescaped in the page. Second, the checkss anti-forgery token is generated using a static site-wide constant (NV_CACHE_PREFIX) instead of a session-bound value, making the token identical for all users and reusable in crafted URLs. This enables attackers to deliver a reflected XSS payload via a simple URL without authentication. The vulnerability was confirmed to allow phishing overlays that capture plaintext credentials. The issue affects versions prior to 4.6.00. The vendor has addressed the root causes by binding the checkss token to the user session and correcting the encoding and rendering process.

CWE-79Improper Neutralization of Input During Web Page Generation (Cross-site Scripting) (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Jul 2026, 10:01 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats