EmailKit <= 1.6.1 - Authenticated (Author+) Arbitrary File Read via Path Traversal
Strategic Overview
- Status
- Patched in 1.6.2
- Affected Plugin
- EmailKit – Email Customizer for WooCommerce & WP
- Affected Version
<= 1.6.1- CVSS
- 6.5Medium
- Weakness type
- CWE-73 · External Control of File Name or Path
- CVE
CVE-2025-14059
At a glance
CVE-2025-14059 is a medium-severity External Control of File Name or Path vulnerability in the EmailKit WordPress plugin, affecting versions <= 1.6.1. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Author level or above. The issue is fixed in version 1.6.2; sites on affected versions should update now. Disclosed January 2026, reported by Dmitrii Ignatyev.
Vulnerability Overview
The EmailKit plugin for WordPress is vulnerable to Arbitrary File Read via Path Traversal in all versions up to, and including, 1.6.1. This is due to missing path validation in the create_template REST API endpoint where user-controlled input from the emailkit-editor-template parameter is passed directly to file_get_contents() without sanitization. This makes it possible for authenticated attackers with Author-level permissions or higher to read arbitrary files on the server, including sensitive configuration files like /etc/passwd and wp-config.php, via the REST API. The file contents are stored in post meta and can be exfiltrated through MetForm's email confirmation feature.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality.
CWE-73: External Control of File Name or Path
The product allows user input to control or influence paths or file names that are used in filesystem operations.
Remediation
Update to version 1.6.2, or a newer patched version
How does WordSec protect against this?
An attacker needs Author access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: EmailKit 1.6.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Related records
Other vulnerabilities in EmailKit – Email Customizer for WooCommerce & WP
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C