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.
Severity
CVSS 3.1
6.0 medium
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:H/A:L
EPSS
0.4% estimated probability of exploitation activity in the next 30 days; 31st percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-22Improper Limitation of a Pathname to a Restricted Directory (Path traversal) CWE-73External Control of File Name or Path
Show the promptExplain CVE-2026-94563 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-94563?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-94563?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-94563 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.