# CVE-2026-1938: Missing authorization in YayMail – WooCommerce Email Customizer

> Authenticated Shop Managers can delete the plugin license key due to missing authorization checks on a REST endpoint.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Feb 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-g6wj-gw42-4345

## What is CVE-2026-1938?

CVE-2026-1938 is a medium-severity missing authorization vulnerability in yaycommerce YayMail – WooCommerce Email Customizer, published on 18 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-1938?


## How do I fix CVE-2026-1938?

No fix has been published for CVE-2026-1938 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-1938 being exploited?

There is no known exploitation of CVE-2026-1938 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-1938 and fix it if it is affected.

What it is: CVE-2026-1938 is a medium-severity missing authorization vulnerability in yaycommerce YayMail – WooCommerce Email Customizer, published on 18 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-1938 in the wild and no public exploit code.

Affected product: yaycommerce YayMail – WooCommerce Email Customizer. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-1938/ (Markdown: https://insights.sbomify.com/CVE-2026-1938/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-1938
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-1938
- OSV: https://osv.dev/vulnerability/CVE-2026-1938

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-1938/
Summaries are generated and may contain mistakes; the official description above is the record.