LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1937: YayMail <= 4.3.2 - Missing Authorization to Authenticated (Shop Manager+) Arbitrary Options Update via 'yaymail_import_state' AJAX Action

The YayMail – WooCommerce Email Customizer plugin for WordPress is vulnerable to unauthorized modification of data that can lead to privilege escalation due to a missing capability check on the `yaymail_import_state` AJAX action 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 update arbitrary options on the WordPress site. This can be leveraged to update the default role for registration to administrator and enable user registration for attackers to gain administrative user access to a vulnerable site.

HighCVSS 7.2Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

YayMail for WooCommerce has a flaw that lets a logged-in Shop Manager or higher change sensitive WordPress settings. That access could be abused to create an administrator account. This is serious for WooCommerce sites where Shop Manager accounts are delegated to staff, agencies, or could be phished.

Executive priority

Treat as high priority for WooCommerce environments. A compromised or misused Shop Manager account could become full site administrator. Prioritize patching or temporary disablement, especially on revenue-generating stores.

Technical view

CVE-2026-1937 is a missing authorization check in the YayMail `yaymail_import_state` AJAX action. Versions up to and including 4.3.2 are described as vulnerable. An authenticated Shop Manager+ user can update arbitrary WordPress options, enabling privilege escalation. CVSS is 7.2 High, CWE-862.

Likely exposure

WordPress WooCommerce sites using YayMail – WooCommerce Email Customizer version 4.3.2 or earlier. Risk is highest where Shop Manager accounts are numerous, shared, delegated externally, or weakly protected.

Exploitation context

The provided sources do not show KEV listing or active exploitation. Exploitation requires authenticated Shop Manager-level access or higher. Impact can include changing registration-related options to obtain administrator access.

Researcher notes

Evidence is based on CVE data, Wordfence, and WordPress Trac references. The bundle names the vulnerable action and impact but does not provide a clearly named fixed version. Avoid assuming active exploitation without additional evidence.

Mitigation direction

  • Check vendor and WordPress plugin guidance for a fixed YayMail release.
  • Update YayMail beyond 4.3.2 if a vendor-fixed version is available.
  • Disable YayMail temporarily if no fix is available and risk is unacceptable.
  • Restrict Shop Manager access to trusted, necessary users only.
  • Enforce strong authentication and MFA for WordPress administrative roles.
  • Review WordPress registration and default-role settings for unauthorized changes.

Validation and detection

  • Inventory WordPress sites using the YayMail plugin.
  • Confirm whether installed YayMail versions are 4.3.2 or earlier.
  • List accounts with Shop Manager or higher privileges.
  • Review recent administrator account creations for suspicious activity.
  • Check registration settings and default new-user role.
  • Review vendor changelog or Trac for authorization checks on `yaymail_import_state`.
Prepared
Confidence
high
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

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 lookup
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-1937 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
7.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H1.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.2High
CVSS 3.1 vector shape for CVE-2026-1937Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
yaycommerceYayMail – WooCommerce Email Customizer0unaffected
Weakness

CWE details

CWE-862

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs