Security readout for executives and security teams
Plain-English summary
This is a low-severity WordPress plugin authorization flaw. A logged-in WooCommerce user with Shop Manager-level access or higher could install and activate the YaySMTP plugin through YayMail functions that lacked proper permission checks. It does not indicate public, unauthenticated compromise or data theft in the provided sources.
Executive priority
Handle during normal vulnerability management unless suspicious account activity exists. Prioritize sites where many users hold Shop Manager access, where plugin changes are not tightly controlled, or where email configuration integrity is business-critical.
Technical view
CVE-2026-1831 affects YayMail – WooCommerce Email Customizer through version 4.3.2. Missing capability checks exist in the yaymail_install_yaysmtp AJAX action and the /yaymail/v1/addons/activate REST endpoint. The issue is classified as CWE-862 with CVSS 3.1 score 2.7, requiring high privileges and enabling limited integrity impact.
Likely exposure
Exposure is limited to WordPress/WooCommerce sites running YayMail version 4.3.2 or earlier and having authenticated Shop Manager-or-higher accounts. Sites without this plugin, without WooCommerce roles, or already updated beyond the affected range are less likely exposed, but should verify installed versions.
Exploitation context
The provided sources do not report active exploitation, and the CVE is not listed as KEV. Abuse requires an authenticated high-privilege WordPress/WooCommerce account. The practical concern is unauthorized installation and activation of YaySMTP, which may affect site configuration and email-related behavior.
Researcher notes
The issue centers on missing capability checks in both an AJAX action and REST endpoint. Source references include the vulnerable 4.3.2 code locations and a WordPress plugin repository changeset. Provided evidence does not include exploit activity or a detailed vendor advisory naming a fixed version.
Mitigation direction
- Inventory WordPress sites using YayMail – WooCommerce Email Customizer.
- Check whether installed YayMail versions are 4.3.2 or earlier.
- Update YayMail according to vendor or WordPress plugin guidance.
- Review Shop Manager and administrator accounts for least-privilege access.
- Monitor plugin installation and activation events for unexpected YaySMTP activity.
Validation and detection
- Confirm the installed YayMail version in WordPress administration or asset inventory.
- Verify whether YaySMTP was installed or activated unexpectedly.
- Review user roles with Shop Manager or higher permissions.
- Check vendor changelog or WordPress plugin repository for the corrected release.
- Confirm authorization checks are present before addon installation or activation actions.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-1831 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Low
- CVSS
- 2.7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N1.21.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
2.7LowVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/a568162a-5a2d-47ab-9dfe-2f2f5f324f0d?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/yaymail/tags/4.3.2/src/Ajax.php#L183CVE reference
- https://plugins.trac.wordpress.org/browser/yaymail/trunk/src/Ajax.php#L183CVE reference
- https://plugins.trac.wordpress.org/browser/yaymail/tags/4.3.2/src/Controllers/AddonController.php#L76CVE reference
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3460087%40yaymail&new=3460087%40yaymail&sfp_email=&sfph_mail=#file11CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.