Skip to main content
Menu
CVEs

NukeViet remote code execution in extension store

Affects NukeViet 4.x installations before 4.6.00 when a GODADMIN administrator uses the extension store. Fixed in 4.6.00.

CVE-2026-61832Published , updated

7.5HighCNA
Exploited
No known exploitation
Fix
Fixed in 4.6.00
Who is exposed
Specific setups only

Summary

A remote attacker who can alter traffic to the NukeViet CMS extension store, without logging in, can run code on the server as the web-server user. The attack works when a GODADMIN opens or uses the store's list, detail, install, or update functions, which causes the server to process a substituted response that writes a PHP file under the web root.

Written by a model

Original description

NukeViet CMS is a multi Content Management System. Prior to 4.6.00, a network attacker who can alter outbound traffic to the extension store can exploit the HTTP client's disabled sslverify setting to substitute a serialized response. Extension-store handlers pass the response to unserialize() without an allowed_classes restriction, allowing an in-tree GuzzleHttp\Cookie\FileCookieJar gadget to write attacker-controlled content to a chosen path. When a GODADMIN opens or uses the store list, detail, install, or update functions, the substituted response can write a PHP file under the web root and execute code as the web-server user. This issue is fixed in version 4.6.00.

Who should check

Teams running NukeViet 4.x CMS installations before 4.6.00 that use the extension store (modules, themes, blocks) and GODADMIN accounts.

“Affected versions < 4.6.00”

github.com

What to do

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

    Affected NukeViet 4.x installations prior to 4.6.00 (affected versions less than 4.6.00). The bundled HTTP client has TLS certificate verification disabled, so the store response is not validated. A privileged GODADMIN must perform a store action (opening the store list, install, update, or detail).
  2. Upgrade to a fixed version: 4.6.00.

  3. Workaround: Enable TLS certificate verification on the HTTP client (set sslverify => true for store/API requests and ensure a valid CA bundle is configured).

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-61832 (NukeViet CMS: PHP Object Injection to RCE in extension store via unverified HTTP response), 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-61832 (entry last updated 2026-11-20):
Affected:
- nukeviet nukeviet: fixed in 4.6.00
Fixed versions: 4.6.00.
Vendor patches: 099ec8c (source: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-9xfw-vx6g-wpmm). Check each asset for these patch ids, not only its version.
Conditions (all must be true for the bug to be hit):
- Affected NukeViet 4.x installations prior to 4.6.00 (affected versions less than 4.6.00). (source: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-9xfw-vx6g-wpmm)
- The bundled HTTP client has TLS certificate verification disabled, so the store response is not validated. (source: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-9xfw-vx6g-wpmm)
- A privileged GODADMIN must perform a store action (opening the store list, install, update, or detail). (source: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-9xfw-vx6g-wpmm)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
Workaround: Enable TLS certificate verification on the HTTP client (set sslverify => true for store/API requests and ensure a valid CA bundle is configured). (source: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-9xfw-vx6g-wpmm)
CISA KEV: CVE-2026-61832 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-61832 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-9xfw-vx6g-wpmm
- https://github.com/nukeviet/nukeviet/commit/099ec8cc4734ba8c1b871653ee454367a07446cc
- https://github.com/nukeviet/nukeviet/releases/tag/4.6.00
- https://nukeviet.vn/vi/news/Tin-tuc/thong-bao-phat-hanh-nukeviet-4-6-00-855.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-61832
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-61832"}.

Affected versions

cve.now Index

21Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure12/25Specific setups only, reachable over the network without a login
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.5/10CVSS 7.5, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 71 if added to CISA KEV
  • Would score about 66 if CISA's SSVC rates exploitation active

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  4. Record last updated

Evidence 6

Questions about CVE-2026-61832

Is CVE-2026-61832 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 bundled HTTP client does not verify TLS certificates, so responses from the extension store are not validated. Through PHP object injection in a GuzzleHttp FileCookieJar gadget, this can lead to writing a PHP file under the web root and running code as the web-server user.

Source: github.com

Which versions are affected by CVE-2026-61832?

nukeviet: before 4.6.00.

Source: cve.now feed data

Am I affected, and how do I check?

NukeViet 4.x versions earlier than 4.6.00 are affected. The problem applies when a GODADMIN administrator performs a routine store action, such as opening the store list or installing, updating, or viewing details. Compare the installed NukeViet version number against 4.6.00 to see where a site falls.

Source: github.com

How do I fix CVE-2026-61832?

Upgrade to NukeViet 4.6.00, which includes patch commit 099ec8c. Until the upgrade is applied, enable TLS certificate verification on the HTTP client by setting sslverify to true for store and API requests and ensuring a valid CA bundle is configured.

Source: github.com

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