CVE-2026-1937
Privilege Escalation in YayMail Plugin via Missing Capability Check
Publication date: 2026-02-18
Last updated on: 2026-04-08
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| yaymail | woocommerce_email_customizer | to 4.3.2 (inc) |
| yaymail | woocommerce_email_customizer | 4.3.3 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-862 | The product does not perform an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The YayMail β WooCommerce Email Customizer plugin for WordPress has a vulnerability due to a missing capability check on the `yaymail_import_state` AJAX action in all versions up to and including 4.3.2.
This flaw allows authenticated attackers with Shop Manager-level access or higher to modify arbitrary options on the WordPress site without proper authorization.
Attackers can exploit this to escalate their privileges by changing the default user registration role to administrator and enabling user registration, thereby gaining administrative access to the site.
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized privilege escalation.
An attacker with Shop Manager-level access can exploit the flaw to update site options arbitrarily, such as setting the default registration role to administrator and enabling user registration.
As a result, attackers can create new administrative users, gaining full control over the WordPress site.
This can lead to complete compromise of the website, including data theft, site defacement, or further malicious activities.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
The vulnerability involves unauthorized modification of data via the `yaymail_import_state` AJAX action, which lacks proper capability checks. Detection would involve monitoring for unauthorized AJAX requests to this action, especially from users with Shop Manager-level access or higher.
Since the vulnerability allows updating arbitrary WordPress options, including changing the default user role to administrator and enabling user registration, suspicious changes to these settings can indicate exploitation.
Suggested commands or methods to detect this vulnerability include:
- Check web server logs or WordPress access logs for POST requests to `admin-ajax.php` with the action parameter `yaymail_import_state`.
- Use command-line tools like `grep` to search for such requests in logs, for example: `grep 'action=yaymail_import_state' /path/to/access.log`.
- Monitor changes in WordPress options related to user roles and registration, e.g., by querying the database for changes in `wp_options` table entries such as `default_role` or `users_can_register`.
- Use WordPress CLI commands to check current settings, for example: `wp option get default_role` and `wp option get users_can_register`.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the YayMail β WooCommerce Email Customizer plugin to version 4.3.3 or later, as this version contains security fixes addressing the vulnerability.
The update enforces proper permission checks on AJAX actions and REST API endpoints, restricting access to users with appropriate capabilities such as `install_plugins`, `activate_plugins`, or `manage_options`.
If immediate updating is not possible, restrict access to the vulnerable AJAX action by limiting user roles or applying firewall rules to block unauthorized AJAX requests targeting `yaymail_import_state`.
Additionally, review and audit user roles and permissions on the WordPress site to ensure no unauthorized administrator accounts have been created.
Disable user registration temporarily if it is not required, to prevent attackers from creating administrative accounts.