YayMail <= 4.3.2 - Missing Authorization to Authenticated (Shop Manager+) License Key Deletion via '/yaymail-license/v1/license/delete' Endpoint
Strategic Overview
- Status
- Patched in 4.3.3
- Affected Plugin
- YayMail – WooCommerce Email Customizer
- Affected Version
<= 4.3.2- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-1938
At a glance
CVE-2026-1938 is a medium-severity Missing Authorization vulnerability in the YayMail WordPress plugin, affecting versions <= 4.3.2. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.3.3; sites on affected versions should update now. Disclosed February 2026, reported by Daniel Basta (whizzu).
Vulnerability Overview
The YayMail – WooCommerce Email Customizer plugin for WordPress is vulnerable to unauthorized license key deletion due to a missing authorization check on the `/yaymail-license/v1/license/delete` REST endpoint in versions up to, and including, 4.3.2. This makes it possible for authenticated attackers, with Shop Manager-level access and above, to delete the plugin's license key via the '/yaymail-license/v1/license/delete' endpoint granted they can obtain the REST API nonce.
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 privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
Reaching this weakness in YayMail <= 4.3.2 takes an account at Shop Manager 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 YayMail the fix is 4.3.3: builds <= 4.3.2 are affected, anything from 4.3.3 onward is not.
Remediation
Update to version 4.3.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: YayMail 4.3.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 YayMail – WooCommerce Email Customizer
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C