Skip to main content
Menu
CVEs

NukeViet path traversal in comment editing allows file deletion

NukeViet CMS releases before 4.5.09 are affected, and 4.5.09 is the fixed version. CVSS scores it 8.7 (High), and no vendor severity is given.

CVE-2026-54065Published , updated

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

Summary

NukeViet CMS is affected through its comment editing and deletion features. A remote attacker who already holds administrator-level login can delete application files outside the upload folder, such as config.php, which causes an outage.

Written by a model

Original description

NukeViet CMS is a multi Content Management System. Prior to 4.5.09, an authenticated administrator can submit a crafted attach value to modules/comment/admin/edit.php. The handler removed a fixed-length upload prefix without validating containment, allowing padding followed by a traversal path to be stored in the database. When the comment is deleted, modules/comment/admin/del.php joins the stored path to NV_UPLOADS_REAL_DIR and passes it to nv_deletefile(), whose realpath() check restricts deletion only to NV_ROOTDIR rather than the upload directory, permitting deletion of application files such as config.php and causing an outage. This issue is fixed in version 4.5.09.

What to do

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

    The malicious attach value is stored, then triggers file deletion when the comment is deleted through the admin comment delete function
  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-54065 (NukeViet CMS: Path Traversal to Arbitrary File Deletion in Edit Comment Function), 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-54065 (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):
- The malicious attach value is stored, then triggers file deletion when the comment is deleted through the admin comment delete function (source: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-c9xg-64p9-f2jj)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, high-privilege login, no user action.
CISA KEV: CVE-2026-54065 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-54065 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-c9xg-64p9-f2jj
- https://github.com/nukeviet/nukeviet/commit/27ba63c32eea2782837b1464a930baf75f0b4d29
- 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-54065
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-54065"}.

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-c9xg-64p9-f2jj
CVE record 1Establishes: The identifier and description.
RecordCVE List · CVE-2026-54065
Other links 2
RepositoryGitHub · nukeviet/nukeviet · Commit 27ba63c3
RepositoryGitHub · nukeviet/nukeviet · Release 4.5.09

Questions about CVE-2026-54065

Is CVE-2026-54065 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 malicious attach value stored in a comment can lead to permanent deletion of arbitrary files within the application root, such as config.php, when the comment is deleted. An authenticated administrator can trigger this through the admin comment delete function.

Source: github.com

Which versions are affected by CVE-2026-54065?

nukeviet: before 4.5.09.

Source: cve.now feed data

Am I affected, and how do I check?

The bug needs a stored malicious attach value in a comment, which is then triggered when that comment is deleted through the admin comment delete function. To check a version, look at the NukeViet release in use; the listed fixed version is 4.5.09, so releases before it are in the affected range.

Source: github.com

How do I fix CVE-2026-54065?

Upgrade NukeViet to 4.5.09, the listed fixed version.

Source: github.com

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