NukeViet arbitrary file write via path traversal in SMTP settings
- Exploited
- No known exploitation
- Fix
- Fixed in 4.6.01
- Who is exposed
- Not reported
Summary
NukeViet CMS lets a logged-in settings-module administrator, reached remotely over the network, upload an S/MIME certificate with a crafted subject name that uses path traversal to write files outside the intended certificate folder. Writes are limited to existing writable directories and permitted file types, but they can overwrite certificate files such as a DKIM private key and, when the curl.cainfo setting is empty, replace cacert.pem, which weakens outbound TLS verification.
Written by a model
Original description
NukeViet CMS is a multi Content Management System. From 4.5.00 until 4.6.01, an authenticated settings-module administrator can upload a PKCS#12 S/MIME certificate whose X.509 Subject CN contains path separators and traversal components. The smimeadd handler in admin/settings/smtp.php applies only an at-sign replacement before using the CN in .key, .crt, and .pem paths beneath data/certs. Traversal can select attacker-chosen paths outside data/certs, but writes remain constrained to already-existing writable directories and the permitted extensions. Within that constraint, attacker-controlled PEM data can overwrite certificate assets, including a DKIM private key; when the curl.cainfo PHP directive is empty, the attacker can also replace cacert.pem and undermine outbound TLS verification. This issue is fixed in version 4.6.01.
What to do
Upgrade to a fixed version: 4.6.01.
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-94563 (NukeViet CMS: Authenticated path traversal to arbitrary file write via S/MIME certificate CN in SMTP settings), 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-94563 (entry last updated 2026-11-20):
Affected:
- nukeviet nukeviet: from 4.5.00, fixed in 4.6.01
Fixed versions: 4.6.01.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-94563 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-94563 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-j79f-jrwm-2f2h
- https://github.com/nukeviet/nukeviet/commit/8f7b3698f1c08b6cdedb500a0d2d2f528d4f0c87
- https://github.com/nukeviet/nukeviet/releases/tag/4.6.01
- https://nukeviet.vn/vi/news/Tin-tuc/thong-bao-phat-hanh-nukeviet-4-6-01-857.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-94563
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-94563"}.Affected versions
- nukeviet nukevietFrom 4.5.00 · fixed in 4.6.01
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6/10CVSS 6.0
- No patch0/5No signal
What would change the score
- Would score about 64 if added to CISA KEV
- Would score about 59 if CISA's SSVC rates exploitation active
- Would score about 28 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 6
| Kind | Source |
|---|---|
| Vendor advisory 2Establishes: Affected and fixed versions. | |
| Advisory | GitHub · nukeviet/nukeviet · Advisory GHSA-j79f-jrwm-2f2h |
| Link | nukeviet.vn · vi/news/Tin-tuc/thong-bao-phat-hanh-nukeviet-4-6-01-857.html |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-94563 |
| Record | NVD · CVE-2026-94563 |
| Other links 2 | |
| Repository | GitHub · nukeviet/nukeviet · Commit 8f7b3698 |
| Repository | GitHub · nukeviet/nukeviet · Release 4.6.01 |
Questions about CVE-2026-94563
Is CVE-2026-94563 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
Which versions are affected by CVE-2026-94563?
nukeviet: from 4.5.00 before 4.6.01.
Source: cve.now feed data
How do I fix CVE-2026-94563?
Upgrade to a fixed version: 4.6.01.
Source: cve.now feed data
Related
- CVE-2026-94567NukeViet CMS: Stored XSS via SVG upload: the sanitizer is blind to markup hidden inside an internal DTD entity
- CVE-2026-94565NukeViet CMS: Unauthenticated Stored XSS in the Contact module
- CVE-2026-54064NukeViet CMS: Multiple Anti-XSS Filter Bypasses Leading to Stored XSS in News Module
- CVE-2026-54065NukeViet CMS: Path Traversal to Arbitrary File Deletion in Edit Comment Function
- CVE-2026-49259NukeViet: stored XSS through comment reply display names
- CVE-2026-41147NukeViet CMS: Stored Cross-Site Scripting (XSS) via insufficient server-side input sanitization in Request class
No corrections so far. Something wrong on this page? Report an error.