Skip to main content
Menu
CVEs

NukeViet unauthenticated reflected XSS in comment module

NukeViet CMS versions before 4.5.09 are affected through the comment module on pages with a comment block, such as news articles. Fixed in 4.5.09.

CVE-2026-48118Published , updated

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

Summary

NukeViet CMS's Comment module has a reflected cross-site scripting flaw that lets a remote attacker, without logging in, make HTML or JavaScript run in a victim's browser via a crafted link the victim must open. An attacker could use this to carry out phishing or perform actions on the same site as the victim.

Written by a model

Original description

NukeViet CMS is a multi Content Management System. Prior to 4.5.09, the Comment module accepts attacker-controlled base64 content in the status_comment parameter through modules/comment/funcs/main.php; modules/comment/comment.php decodes it with nv_base64_decode() and assigns it to STATUS_COMMENT without output escaping. The required checkss token was derived from the site-wide NV_CACHE_PREFIX rather than NV_CHECK_SESSION, so a token disclosed in public comment markup could be reused across sessions in a crafted URL. An unauthenticated attacker can therefore cause decoded HTML or JavaScript to render in a victim's browser and perform phishing or same-origin actions. This issue is fixed in version 4.5.09.

What to do

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

    A page with a comment block (for example a news article) must be available so the checkss token can be read from its HTML.
  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-48118 (NukeViet CMS: Unauthenticated Reflected XSS in Comment Module), 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-48118 (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):
- A page with a comment block (for example a news article) must be available so the checkss token can be read from its HTML. (source: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-mxpf-qgg6-v3ff)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-48118 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-48118 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-mxpf-qgg6-v3ff
- https://github.com/nukeviet/nukeviet/commit/c8a0d90887044735a65c4810b46b5fb3d2438022
- 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-48118
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-48118"}.

Affected versions

cve.now Index

20Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure12/25Specific setups only, reachable over the network without a login
  • 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

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-mxpf-qgg6-v3ff
CVE record 1Establishes: The identifier and description.
RecordCVE List · CVE-2026-48118
Other links 2
RepositoryGitHub · nukeviet/nukeviet · Commit c8a0d908
RepositoryGitHub · nukeviet/nukeviet · Release 4.5.09

Questions about CVE-2026-48118

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

The comment module reflects input without proper filtering, so script or HTML can render in a visitor's browser within the site's origin. The facts confirm a phishing overlay that captured plaintext credentials and sent them to an attacker-controlled server.

Source: github.com

Which versions are affected by CVE-2026-48118?

nukeviet: before 4.5.09.

Source: cve.now feed data

Am I affected, and how do I check?

Installations of NukeViet CMS earlier than 4.5.09 fall in the affected range. The issue needs a page with a comment block, such as a news article, where the checkss token can be read from the HTML source. Compare the installed version against 4.5.09 to see where an installation stands.

Source: github.com

How do I fix CVE-2026-48118?

Upgrade NukeViet CMS to 4.5.09 or later, which is the listed fixed version.

Source: github.com

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