CVE-2026-94563: NukeViet CMS: Authenticated path traversal to arbitrary file write via S/MIME certificate CN in SMTP settings

Published Nov 20, 2026
·
Updated

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.

Affected Software

1 affected component
NukeViet NukeViet CMS>=4.5.00<4.6.01

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.6.01

Event History

Nov 20, 2026
CVE Published
via MITRE·06:44 PM
Data Sourced
via MITRE·06:44 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:18 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

An authenticated administrator with access to the settings module is required. The attacker must be able to upload a crafted PKCS#12 S/MIME certificate through the SMTP settings handler.

2

Are arbitrary files writable anywhere on the server?

No. Path traversal can target locations outside data/certs, but writes are limited to paths in already-existing writable directories and to the .key, .crt, and .pem extensions used by the handler.

3

What assets are most concerning if the issue is exploited?

An attacker can overwrite certificate-related assets, including a DKIM private key. If the PHP curl.cainfo directive is empty, they may also replace cacert.pem, undermining outbound TLS certificate verification.

4

What should be done if patching cannot happen immediately?

Restrict settings-module administrator access and prevent untrusted administrators from uploading S/MIME certificates through SMTP settings. Review writable directories and certificate assets with .key, .crt, or .pem extensions for unexpected changes.

5

Which versions are affected and what version fixes it?

Versions from 4.5.00 until 4.6.01 are affected. The issue is fixed in version 4.6.01.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203