HomeWordPress vulnerabilitiesEmailKit
EmailKit vulnerabilities
EmailKit has 4 known vulnerabilities in this database. The most recent published record is dated 5 May 2026.
- Known vulnerabilities
- 4
- Active installs
- 70,000+
- Latest version
- 1.6.9
- Last updated
- 13 Sep 2026
- Most recent
- 5 May 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Arbitrary file read CVE-2026-5957 | Medium 6.5 | Up to 1.6.5 | Fixed in a later version (latest 1.6.9) | 5 May 2026 |
| Arbitrary file read CVE-2026-3474 | Medium 4.9 | Up to 1.6.3 | Fixed in a later version (latest 1.6.9) | 21 Mar 2026 |
| Broken access control CVE-2026-1925 | Medium 4.3 | Up to 1.6.2 | Fixed in a later version (latest 1.6.9) | 18 Feb 2026 |
| Arbitrary file read CVE-2025-14059 | Medium 6.5 | Up to 1.6.1 | Fixed in a later version (latest 1.6.9) | 7 Jan 2026 |
Read the published descriptions
- CVE-2026-5957, 5 May 2026
- The EmailKit plugin for WordPress is vulnerable to Arbitrary File Read in all versions up to and including 1.6.5. This is due to a flawed path traversal validation in the create_template() method of the CheckForm class, where realpath() is called on the allowed base directory (wp-content/uploads/emailkit/templates/) which may not exist, causing it to return false. In PHP 8.x, strpos($real_path, false) implicitly converts false to an empty string, and strpos() with an empty needle always returns 0, causing the check strpos(...) !== 0 to evaluate to false and bypassing the path validation entirely. This makes it possible for authenticated attackers, with Author-level access and above, to read arbitrary files from the server, including sensitive files such as wp-config.php, by supplying an absolute path to the emailkit-editor-template REST API parameter. CVE record
- CVE-2026-3474, 21 Mar 2026
- The EmailKit - Email Customizer for WooCommerce & WP plugin for WordPress is vulnerable to arbitrary file read via path traversal in all versions up to, and including, 1.6.3. This is due to the action() function in the TemplateData class passing user-supplied input from the 'emailkit-editor-template' REST API parameter directly to file_get_contents() without any path validation, sanitization, or restriction to an allowed directory. This makes it possible for authenticated attackers, with Administrator-level access, to read arbitrary files on the server (such as /etc/passwd or wp-config.php) by supplying a traversal path. The file contents are stored as post meta and can subsequently be retrieved via the fetch-data REST API endpoint. Notably, the CheckForm class in the same plugin implements proper path validation using realpath() and directory restriction, demonstrating that the developer was aware of the risk but failed to apply the same protections to the TemplateData endpoint. CVE record
- CVE-2026-1925, 18 Feb 2026
- The EmailKit - Email Customizer for WooCommerce & WP plugin for WordPress is vulnerable to unauthorized data modification due to a missing capability check on the 'update_template_data' function in all versions up to, and including, 1.6.2. This makes it possible for authenticated attackers, with Subscriber-level access and above, to modify the title of any post on the site, including posts, pages, and custom post types. CVE record
- CVE-2025-14059, 7 Jan 2026
- 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. CVE record
What to do if you run EmailKit
If you run EmailKit, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new EmailKit vulnerabilities
Free. We email you when a new vulnerability is published for EmailKit, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.