LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1943: YayMail <= 4.3.2 - Authenticated (Shop Manager+) Stored Cross-Site Scripting via Template Elements

The YayMail – WooCommerce Email Customizer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via settings in all versions up to, and including, 4.3.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Shop Manager-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.

MediumCVSS 4.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

YayMail for WooCommerce has a stored cross-site scripting flaw in versions up to 4.3.2. A trusted store user with Shop Manager or higher privileges could save malicious script in email template settings. It affects only multisite sites and sites where unfiltered_html is disabled. Business risk is limited but real for compromised or overly broad store accounts.

Executive priority

Handle in the normal vulnerability management cycle, with faster action for ecommerce sites using multisite or broad Shop Manager access. This is not currently evidenced as mass-exploited, but stored XSS can affect administrative trust and customer-facing operations if privileged accounts are compromised.

Technical view

CVE-2026-1943 is CWE-79 stored XSS caused by insufficient input sanitization and output escaping in YayMail template elements/settings. CVSS is 4.4, requiring network access, high privileges, and high attack complexity. Successful injection executes when a user accesses the affected page. Public references point to TemplateController and template rendering files in version 4.3.2.

Likely exposure

Exposure is limited to WordPress WooCommerce sites running YayMail through version 4.3.2, with multisite enabled or unfiltered_html disabled, and users holding Shop Manager-level access or higher. Single-site installations where unfiltered_html remains available are described as not affected by this issue.

Exploitation context

No active exploitation is indicated in the provided sources, and the CVE is not in KEV. Exploitation requires an authenticated privileged user, reducing broad internet risk. The main concern is malicious insiders, compromised Shop Manager accounts, or role misconfiguration that allows unnecessary access to YayMail template settings.

Researcher notes

Sources identify CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N and CWE-79. The affected range is stated as all versions through 4.3.2. The bundle includes code references and a Trac changeset, but does not clearly name a fixed release version. Avoid assuming exploit availability or patch details beyond those sources.

Mitigation direction

  • Inventory WordPress sites using YayMail and identify versions up to 4.3.2.
  • Prioritize multisite installations and sites with unfiltered_html disabled.
  • Update YayMail beyond 4.3.2 when vendor or WordPress plugin guidance confirms a fixed release.
  • Restrict Shop Manager and higher roles to trusted users only.
  • Review YayMail template settings for unexpected script-like content.
  • Monitor vendor, Wordfence, and WordPress plugin repository guidance for remediation details.

Validation and detection

  • Confirm installed YayMail version on each WooCommerce site.
  • Check whether the site is WordPress multisite.
  • Verify whether unfiltered_html is disabled for relevant users.
  • Review users with Shop Manager, Administrator, or equivalent access.
  • Inspect YayMail template elements for unauthorized or suspicious saved content.
  • Confirm remediation status against vendor or WordPress repository release notes.
Prepared
Confidence
high
Sources
7

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-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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
cve · low confidence lookup

CVE-2026-1943 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
Medium
CVSS
4.4 (3.1)
Known Exploited
No
Published

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

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
6Source 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
4.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N1.32.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.4Medium
CVSS 3.1 vector shape for CVE-2026-1943Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Products and packages named in the record

VendorProductVersion / packageStatus
yaycommerceYayMail – WooCommerce Email Customizer0unaffected
Weakness

CWE details

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

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.