Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-1831: CWE-862 Missing Authorization in yaycommerce YayMail – WooCommerce Email Customizer

0
Low
VulnerabilityCVE-2026-1831cvecve-2026-1831cwe-862
Published: Wed Feb 18 2026 (02/18/2026, 07:25:41 UTC)
Source: CVE Database V5
Vendor/Project: yaycommerce
Product: YayMail – WooCommerce Email Customizer

Description

The YayMail - WooCommerce Email Customizer plugin for WordPress is vulnerable to unauthorized plugin installation and activation due to missing capability checks on the 'yaymail_install_yaysmtp' AJAX action and `/yaymail/v1/addons/activate` REST endpoint in all versions up to, and including, 4.3.2. This makes it possible for authenticated attackers, with Shop Manager-level access and above, to install and activate the YaySMTP plugin.

AI-Powered Analysis

AILast updated: 02/18/2026, 08:01:27 UTC

Technical Analysis

CVE-2026-1831 identifies a missing authorization vulnerability (CWE-862) in the YayMail – WooCommerce Email Customizer plugin for WordPress, specifically affecting all versions up to 4.3.2. The flaw exists because the plugin fails to perform proper capability checks on the 'yaymail_install_yaysmtp' AJAX action and the '/yaymail/v1/addons/activate' REST endpoint. This omission allows authenticated users with Shop Manager-level access or higher to install and activate the YaySMTP plugin without sufficient privileges. The vulnerability does not require user interaction beyond authentication and is exploitable remotely over the network (AV:N). The CVSS 3.1 base score is 2.7, reflecting low severity due to the requirement of high privileges (PR:H) and no impact on confidentiality or availability, only a limited integrity impact (I:L). While the direct impact is limited to unauthorized plugin activation, this could be leveraged as a stepping stone for further attacks if the activated plugin contains vulnerabilities or malicious code. No public exploits have been reported, and no patches are currently linked, indicating a need for vendor response. The vulnerability affects WooCommerce sites using YayMail, a popular email customization plugin, which is widely used in e-commerce environments.

Potential Impact

For European organizations, this vulnerability poses a risk primarily in environments where Shop Manager roles are assigned to users who may not be fully trusted or where internal controls are lax. Unauthorized plugin installation can lead to the introduction of malicious plugins or unintended functionality, potentially compromising site integrity or enabling further attacks such as data manipulation or privilege escalation. Although the immediate impact is low, the ability to activate plugins without proper authorization could facilitate supply chain attacks or persistence mechanisms. E-commerce sites in Europe relying on WooCommerce and YayMail may face reputational damage, operational disruption, or compliance issues if exploited. The impact is more significant in organizations with complex user role assignments or where internal threat actors exist. Given the widespread use of WooCommerce in countries like Germany, the UK, France, and the Netherlands, the threat is relevant to many European businesses operating online stores.

Mitigation Recommendations

Organizations should immediately audit user roles and restrict Shop Manager privileges to trusted personnel only, minimizing the risk of unauthorized actions. Until an official patch is released, consider disabling or restricting access to the vulnerable AJAX action and REST endpoints via web application firewalls or custom code filters. Monitoring plugin installation and activation logs can help detect suspicious activity early. Employ the principle of least privilege by reviewing and tightening WordPress role capabilities, especially for Shop Manager users. Regularly update all WordPress plugins and themes to their latest versions once patches become available. Additionally, consider implementing multi-factor authentication for all administrative roles to reduce the risk of credential compromise. For critical e-commerce sites, isolating plugin management to higher privilege roles such as Administrator can further reduce exposure. Finally, maintain backups and incident response plans to quickly recover from any potential compromise stemming from this vulnerability.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2026-02-03T14:41:20.453Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69956e1c80d747be20503e1a

Added to database: 2/18/2026, 7:45:32 AM

Last enriched: 2/18/2026, 8:01:27 AM

Last updated: 2/20/2026, 11:28:24 PM

Views: 65

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats