EmailKit at a glance
- 5 publicly disclosed vulnerabilities. The most recent was disclosed on May 4, 2026.
- Ranked #562 by popularity on WordPress.org (70,000+ active installs).
- The latest version is 1.7.0 (released Nov 3, 2026). The most recent security fix shipped in 1.6.6.
- Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
- The first thing to do: update to the latest version and turn on automatic updates.
Check your EmailKit version
Enter the EmailKit version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.
Your version number is compared on this page only. It is not sent anywhere.
Get an email when a new vulnerability is disclosed
We'll tell you when a new vulnerability is disclosed in “EmailKit”, with the version that fixes it. Free, email address only, stop any time.
We use your email address only for these alerts. Privacy policy
Want every plugin and theme on your site checked daily?
With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.
How to check whether your site is affected
- 1
Find your version
In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “EmailKit”.
- 2
Compare it with the list below
If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.
- 3
Update
Click “Update now” to move to the latest version (1.7.0). Taking a backup first is a good idea.
- 4
Turn on automatic updates
On the same screen, click “Enable auto-updates” so future fixes are installed automatically.
Known EmailKit vulnerabilities
EmailKit <= 1.6.5 - Authenticated (Author+) Arbitrary File Read via 'emailkit-editor-template' REST Parameter
Arbitrary file read or deletion · CVE-2026-5957
Affected versions: ≤ 1.6.5
Fixed in: 1.6.6
Severity: Medium 6.5 · Disclosed May 4, 2026
EmailKit <= 1.6.3 - Authenticated (Administrator+) Path Traversal via 'emailkit-editor-template' REST API Parameter
Arbitrary file read or deletion · CVE-2026-3474
Affected versions: ≤ 1.6.3
Fixed in: 1.6.4
Severity: Medium 4.9 · Disclosed Mar 20, 2026
EmailKit – Email Customizer for WooCommerce & WP <= 1.6.2 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Post Title Modification
Missing authorization · CVE-2026-1925
Affected versions: ≤ 1.6.2
Fixed in: 1.6.3
Severity: Medium 4.3 · Disclosed Feb 17, 2026
EmailKit <= 1.6.1 - Authenticated (Author+) Arbitrary File Read via Path Traversal
Arbitrary file read or deletion · CVE-2025-14059
Affected versions: ≤ 1.6.1
Fixed in: 1.6.2
Severity: Medium 6.5 · Disclosed Jan 6, 2026
EmailKit <= 1.6.0 - Missing Authorization to Authenticated (Author+) Arbitrary Content Deletion
Missing authorization · CVE-2025-60106
Affected versions: ≤ 1.6.0
Fixed in: 1.6.1
Severity: Medium 4.3 · Disclosed Sep 26, 2025
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| EmailKit <= 1.6.5 - Authenticated (Author+) Arbitrary File Read via 'emailkit-editor-template' REST ParameterArbitrary file read or deletion · CVE-2026-5957 | ≤ 1.6.5 | 1.6.6 | Medium 6.5 | May 4, 2026 |
| EmailKit <= 1.6.3 - Authenticated (Administrator+) Path Traversal via 'emailkit-editor-template' REST API ParameterArbitrary file read or deletion · CVE-2026-3474 | ≤ 1.6.3 | 1.6.4 | Medium 4.9 | Mar 20, 2026 |
| EmailKit – Email Customizer for WooCommerce & WP <= 1.6.2 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Post Title ModificationMissing authorization · CVE-2026-1925 | ≤ 1.6.2 | 1.6.3 | Medium 4.3 | Feb 17, 2026 |
| EmailKit <= 1.6.1 - Authenticated (Author+) Arbitrary File Read via Path TraversalArbitrary file read or deletion · CVE-2025-14059 | ≤ 1.6.1 | 1.6.2 | Medium 6.5 | Jan 6, 2026 |
| EmailKit <= 1.6.0 - Missing Authorization to Authenticated (Author+) Arbitrary Content DeletionMissing authorization · CVE-2025-60106 | ≤ 1.6.0 | 1.6.1 | Medium 4.3 | Sep 26, 2025 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: May 4, 2026.
Most common weaknesses in EmailKit
Arbitrary file read or deletion
3 issues
An attacker can read or delete files on the server. Deleting a configuration file can take the site offline, and reading one can expose passwords.
Missing authorization
2 issues
Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.
Frequently asked questions
Is EmailKit safe to use?
EmailKit is a well-known plugin with 70,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (1.7.0) and turn on automatic updates.
How do I find which version of EmailKit my site is running?
In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.
Could updating break my site?
Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.
Can I check all my other plugins too?
Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.
Check every plugin and theme automatically, every day
Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.
Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.