CVE-2026-54065

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

• Any file readable by the web server process within NV_ROOTDIR can be permanently deleted.
• Deleting config.php causes a full application outage and exposes the install wizard.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2026-54065 has a CVSS score of 8.7 (High). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.6.00); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

Added nv_is_file() validation before processing the attach value. This function uses realpath() and a regex check to ensure the file resolves to a path within the intended upload directory, rejecting any traversal attempts.

// Fixed code
$attach = $nv_Request->get_string('attach', 'post', '');
if (!empty($attach) and nv_is_file($attach, NV_UPLOADS_DIR . '/' . $module_upload)) {
    $attach = substr($attach, strlen(NV_BASE_SITEURL . NV_UPLOADS_DIR . '/' . $module_upload . '/'));
} else {
    $attach = '';
}

1. What is CVE-2026-54065? CVE-2026-54065 is a high-severity path traversal vulnerability in nukeviet/nukeviet (composer), affecting versions < 4.6.00. It is fixed in 4.6.00. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2026-54065? CVE-2026-54065 has a CVSS score of 8.7 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of nukeviet/nukeviet are affected by CVE-2026-54065? nukeviet/nukeviet (composer) versions < 4.6.00 is affected.
4. Is there a fix for CVE-2026-54065? Yes. CVE-2026-54065 is fixed in 4.6.00. Upgrade to this version or later.
5. Is CVE-2026-54065 exploitable, and should I be worried? Whether CVE-2026-54065 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-54065 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-54065? Upgrade nukeviet/nukeviet to 4.6.00 or later.

Other vulnerabilities in nukeviet/nukeviet