dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-1937

HIGH · 7.2 CVSS v3.1 Published 2026-02-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
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.

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 confidence

The YayMail WooCommerce Email Customizer plugin for WordPress lacks a capability check on the `yaymail_import_state` AJAX action, allowing authenticated users with Shop Manager-level permissions or higher to modify arbitrary WordPress options. Attackers can change the default user registration role to Administrator and enable user registration, effectively escalating privileges to admin access.

MitigationUpdate the YayMail plugin to version 4.3.3 or later which includes proper capability checks on the AJAX action. If immediate update is not possible, consider restricting AJAX endpoint access or implementing a WAF rule to block unauthorized option modifications.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify YayMail plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'YayMail - WooCommerce Email Customizer' or check wp-content/plugins directory for yaymail folder
    Affected if Plugin is not installed means not affected
  2. Check installed YayMail version
    In WordPress admin Plugins list, look for the version number under YayMail, or inspect the main plugin file header in wp-content/plugins/yaymail/yaymail.php for 'Version:' field
    Affected if Version is present and less than 4.3.3 indicates potentially vulnerable
  3. Confirm user registration is enabled
    Go to WordPress admin Settings > General > 'Membership' section and check if 'Anyone can register' is enabled
    Affected if User registration is enabled AND YayMail < 4.3.3 is installed means vulnerable configuration exists
  4. Verify current user roles with elevated permissions
    In WordPress admin Users > All Users, check if any accounts have 'Shop Manager' role (common in WooCommerce setups)
    Affected if Site has Shop Manager users AND YayMail < 4.3.3 creates attack surface
  5. Check for unauthorized admin accounts
    In WordPress admin Users > All Users, review all accounts with Administrator role, looking for unexpected or unknown accounts
    Affected if Unexpected admin accounts may indicate this vulnerability was exploited

Environment is affected if YayMail plugin versions below 4.3.3 are installed on a WordPress site with WooCommerce and either user registration enabled or existing Shop Manager-level users present.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the YayMail plugin to version 4.3.3 or later which includes proper capability checks on the AJAX action. If immediate update is not possible, consider restricting AJAX endpoint access or implementing a WAF rule to block unauthorized option modifications.

Recommended fix Moderate confidence

YayMail version 4.3.3 or later

  1. 1. Log in to the WordPress admin dashboard with administrator privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the YayMail – WooCommerce Email Customizer plugin
  4. 4. Check if an update to version 4.3.3 or later is available
  5. 5. If update available, click 'Update Now' to install the patched version
  6. 6. If no update shown, manually download the latest version from WordPress.org plugin repository and upload via Plugins > Add New > Upload Plugin
  7. 7. Verify the updated version number after installation

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1937 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1937 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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