EmailKit – Email Customizer for WooCommerce & WP <= 1.6.2 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Post Title Modification
Strategic Overview
- Status
- Patched in 1.6.3
- Affected Plugin
- EmailKit – Email Customizer for WooCommerce & WP
- Affected Version
<= 1.6.2- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-1925
At a glance
CVE-2026-1925 is a medium-severity Missing Authorization vulnerability in the EmailKit WordPress plugin, affecting versions <= 1.6.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.6.3; sites on affected versions should update now. Disclosed February 2026, reported by Chiao-Lin Yu (Steven Meow).
Vulnerability Overview
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.
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.
CWE-862: Missing Authorization
EmailKit <= 1.6.2 carries this weakness at update_template_data, and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For EmailKit the fix is 1.6.3: builds <= 1.6.2 are affected, anything from 1.6.3 onward is not.
Remediation
Update to version 1.6.3, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: EmailKit 1.6.3 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in EmailKit – Email Customizer for WooCommerce & WP
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C