Skip to main content
Menu
CVEs

NukeViet remote code execution via image upload filter bypass

Affects NukeViet 4.6.01 and earlier, and 4.5.11 and earlier, on Apache with mod_php, short_open_tag enabled, and AddHandler for .php files. Fixed in 4.5.12 and 4.6.02.

CVE-2026-94597Published , updated

7.5HighCNA
Exploited
No known exploitation
Fix
Fixed in 4.5.12, 4.6.02
Who is exposed
Specific setups only

Summary

NukeViet CMS has an image-upload flaw that lets an attacker who can reach the upload feature store a disguised PHP file, which can run operating-system commands as the web-server user. This applies only to Apache mod_php systems configured with short_open_tag and a PHP extension handler. An attacker can reach the flaw remotely over the network with low-privilege login, by uploading an image with appended PHP short-tag code under a double-extension filename that gets past the image check and extension filter.

Written by a model

Original description

NukeViet CMS is a multi Content Management System. Prior to 4.5.12 and 4.6.02, an attacker who can reach an image-upload flow can upload a valid image with appended PHP short-tag code and a double-extension filename. NukeViet\Files\Upload::save_file() relied on verify_image(), which missed the <? short-open tag, while filename handling preserved embedded dots, validation inspected only the final extension, and an .htaccess rule blocked PHP extensions only at the end of the URI. On Apache mod_php systems configured with short_open_tag and a PHP extension handler, the stored polyglot can execute as PHP and run operating-system commands as the web-server user; PHP-FPM, nginx, and end-anchored handler configurations are not exposed to the execution step. This issue is fixed in versions 4.5.12 and 4.6.02.

Who should check

Teams running NukeViet 4.6.01 or earlier, or 4.5.11 or earlier, on Apache with mod_php and short_open_tag On, with image uploads enabled for avatar, banner, or comments.

Not fixed by: Workarounds are mitigations only; upgrading is the robust fix.

“<=4.6.01, <=4.5.11”

github.com

What to do

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

    Apache with mod_php, short_open_tag enabled, and AddHandler application/x-httpd-php for .php files. Attacker can reach an image upload flow: admin uploader, avatar, banner, or comment attachments when enabled. Affected NukeViet versions: 4.6.01 and earlier, or 4.5.11 and earlier.
  2. Upgrade to a fixed version: 4.5.12, 4.6.02.

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-94597 (NukeViet CMS: Remote Code Execution via image-upload bypass chain (PHP short-tag detection bypass + double-extension filename)), 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-94597 (entry last updated 2026-11-20):
Affected:
- nukeviet nukeviet: fixed in 4.5.12; from 4.6.00, fixed in 4.6.02
Fixed versions: 4.5.12, 4.6.02.
Conditions (all must be true for the bug to be hit):
- Apache with mod_php, short_open_tag enabled, and AddHandler application/x-httpd-php for .php files. (source: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-2cvj-x8hg-6wcq)
- Attacker can reach an image upload flow: admin uploader, avatar, banner, or comment attachments when enabled. (source: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-2cvj-x8hg-6wcq)
- Affected NukeViet versions: 4.6.01 and earlier, or 4.5.11 and earlier. (source: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-2cvj-x8hg-6wcq)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-94597 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-94597 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-2cvj-x8hg-6wcq
- https://github.com/nukeviet/nukeviet/commit/5703071071ddb7400a0704da4c9bb4da6c6ddb23
- https://github.com/nukeviet/nukeviet/releases/tag/4.6.02
- https://nukeviet.vn/vi/news/Tin-tuc/thong-bao-phat-hanh-nukeviet-4-6-02-858.html
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-94597
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-94597"}.

Affected versions

cve.now Index

16Pof 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
  • Severity7.5/10CVSS 7.5
  • No patch0/5No signal

What would change the score

  • Would score about 66 if added to CISA KEV
  • Would score about 61 if CISA's SSVC rates exploitation active
  • Would score about 23 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 7

KindSource
Vendor advisory 2Establishes: Affected and fixed versions.
AdvisoryGitHub · nukeviet/nukeviet · Advisory GHSA-2cvj-x8hg-6wcq
Linknukeviet.vn · vi/news/Tin-tuc/thong-bao-phat-hanh-nukeviet-4-6-02-858.html
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-94597
RecordNVD · CVE-2026-94597
Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
ExploitGitHub · canhieu/CVE-2026-94597-poc · Repository
Other links 2
RepositoryGitHub · nukeviet/nukeviet · Commit 57030710
RepositoryGitHub · nukeviet/nukeviet · Release 4.6.02

Questions about CVE-2026-94597

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

An image-upload check can be bypassed so that a PHP file is saved with a double extension and still runs as code. This gives arbitrary OS command execution as the web-server user, which can lead to full site compromise and disclosure of database credentials.

Source: github.com

Which versions are affected by CVE-2026-94597?

nukeviet: before 4.5.12; from 4.6.00 before 4.6.02.

Source: cve.now feed data

Am I affected, and how do I check?

Affected NukeViet versions are 4.6.01 and earlier, and 4.5.11 and earlier. The setup also matters: it requires Apache with mod_php, short_open_tag set to On, and AddHandler application/x-httpd-php for .php files. Check the NukeViet version in use, the short_open_tag value in the PHP configuration, and the Apache AddHandler directive.

Source: github.com

How do I fix CVE-2026-94597?

Upgrade to NukeViet 4.5.12 on the 4.5 branch or 4.6.02 on the 4.6 branch.

Source: github.com

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