Security readout for executives and security teams
Plain-English summary
A WordPress WooCommerce plugin, YayMail, allowed certain logged-in store users to delete the plugin license key without proper authorization. This does not indicate customer data theft or site takeover, but it can disrupt licensing, updates, or paid functionality. The issue affects YayMail versions up to and including 4.3.2 according to the source bundle.
Executive priority
Treat as a medium-priority maintenance and access-control issue. Prioritize ecommerce sites with many delegated shop managers or outside operators. It is not supported by the provided sources as an emergency compromise indicator.
Technical view
CVE-2026-1938 is a CWE-862 missing authorization issue in YayMail’s `/yaymail-license/v1/license/delete` REST endpoint. The report states authenticated attackers with Shop Manager-level access or higher, and a REST API nonce, could delete the plugin license key. The CVSS vector in the bundle conflicts with that prerequisite by listing PR:N.
Likely exposure
Exposure is limited to WordPress/WooCommerce sites running YayMail up to 4.3.2, especially where Shop Manager-level accounts are delegated to staff or third parties. The documented impact is license key deletion, not remote code execution, credential theft, or database compromise.
Exploitation context
The source bundle does not show CISA KEV listing or public evidence of active exploitation. Exploitation requires access conditions described by Wordfence: Shop Manager-level authentication or above and the ability to obtain a REST API nonce.
Researcher notes
Primary uncertainty is the mismatch between the narrative requiring authenticated Shop Manager access and the CVSS vector showing PR:N. The WordPress Trac references and changeset indicate relevant code locations, but the bundle does not clearly name a fixed version.
Mitigation direction
- Check vendor or WordPress plugin guidance for the fixed YayMail release.
- Update YayMail if a newer trusted version is available.
- Restrict Shop Manager and administrator access to trusted users only.
- Remove unused or third-party WooCommerce management accounts.
- Monitor YayMail license status after remediation.
Validation and detection
- Inventory WordPress sites using YayMail.
- Confirm whether installed YayMail versions are 4.3.2 or earlier.
- Review users with Shop Manager or administrator roles.
- Check logs for requests to `/yaymail-license/v1/license/delete`.
- Verify the plugin license key remains present after update.
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-1938 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
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/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:N/UI:N/S:U/C:N/I:L/A:N3.91.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/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/6ce57b12-2241-416b-b466-aa06ca8c7551?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/yaymail/tags/4.3.2/src/License/RestAPI.php#L142CVE reference
- https://plugins.trac.wordpress.org/browser/yaymail/trunk/src/License/RestAPI.php#L142CVE reference
- https://plugins.trac.wordpress.org/changeset/3460087/CVE 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.