NukeViet: Path Traversal to Arbitrary File Deletion in Edit Comment Function

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary Path Traversal to Arbitrary File Deletion in the Edit Comment admin function. An authenticated administrator can delete arbitrary files within the application root (e.g., config.php) by injecting a crafted attach parameter, rendering the application inoperable. Affected Component modules/comment/admin/edit.php Root Cause In the vulnerable version, the attach parameter received via HTTP POST was not validated before being processed: substr() strips the first N characters (equal to the length of the upload URL prefix, e.g. 26 chars for /nukeviet/uploads/comment/). By padding the payload with exactly 26 arbitrary characters followed by a path traversal sequence, an attacker can store ../../<target directly into the database. When the comment is subsequently deleted, del.php reads attach from the database and calls: nvdeletefile() resolves the path via realpath() and only verifies the result is within NVROOTDIR — it does not restrict deletion to the uploads directory — allowing…

Published by the source

13 Jul 2026, 17:55 UTC

Last modified by the source

13 Jul 2026, 17:55 UTC

Source last checked

26 Oct 2026, 14:50 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-c9xg-64p9-f2jj

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-54065

Advisory: NukeViet: Path Traversal to Arbitrary File Deletion in Edit Comment Function
IDs: CVE-2026-54065, GHSA-c9xg-64p9-f2jj
Record: https://patchnext.com/advisories/cve-2026-54065 (revision 1, source checked 26 Oct 2026, 14:50 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: nukeviet/nukeviet 4.6.00. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist nukeviet/nukeviet: affected < 4.6.00; fixed in 4.6.00

## Suggested inspection (read-only)
- Packagist nukeviet/nukeviet: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on nukeviet/nukeviet.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-c9xg-64p9-f2jj (GitHub-reviewed advisory GHSA-c9xg-64p9-f2jj lists affected ranges: Packagist nukeviet/nukeviet >=0 <4.6.00)

Commands are suggestions: review each one before running it.