CVE-2026-1938
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe YayMail – WooCommerce Email Customizer plugin for WordPress is vulnerable to unauthorized license key deletion due to a missing authorization check on the `/yaymail-license/v1/license/delete` REST endpoint in versions up to, and including, 4.3.2. This makes it possible for authenticated attackers, with Shop Manager-level access and above, to delete the plugin's license key via the '/yaymail-license/v1/license/delete' endpoint granted they can obtain the REST API nonce.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe YayMail – WooCommerce Email Customizer plugin for WordPress versions up to 4.3.2 contains a broken access control vulnerability in the `/yaymail-license/v1/license/delete` REST API endpoint. The endpoint lacks proper authorization validation, allowing any authenticated user with Shop Manager-level permissions or higher to delete the plugin's license key by supplying a valid REST API nonce.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify YayMail plugin is installedNavigate to WordPress admin > Plugins and locate the YayMail - WooCommerce Email Customizer plugin, or check the plugins directory for yaymail folder and read the main plugin file header for versionAffected if Plugin is installed and version is 4.3.2 or lower
-
Confirm installed version numberRead the plugin version from the plugin header comment in the main file (usually yaymail.php) or from the WordPress plugins admin pageAffected if Version is 4.3.2 or below (versions prior to the 4.3.3 patch)
-
Identify users with Shop Manager roleIn WordPress admin, go to Users > All Users and filter or check for users with Shop Manager role, or query the wp_usermeta table for wp_capabilities containing 'shop_manager'Affected if Any user account with Shop Manager role or higher exists on the site
-
Test vulnerable REST API endpoint accessibilitySend a REST API request to /wp-json/yaymail-license/v1/license/delete with a valid nonce from any authenticated session (even without proper authorization)Affected if The endpoint accepts the request and processes it without verifying the user has administrator-level permissions
-
Check current license key statusNavigate to YayMail settings page in WordPress admin, or query the wp_options table for option_name containing 'yaymail_license'Affected if License key is present and was potentially deletable by unauthorized users
You are affected if the YayMail plugin is installed at version 4.3.2 or lower and any authenticated user with Shop Manager-level permissions exists on the site, as the license deletion REST endpoint accepts requests without proper authorization validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate to version 4.3.3 or later which implements proper authorization checks on the license deletion REST endpoint to verify user permissions before processing the request.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1938 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-1938 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data