# CVE-2025-11237: Make Email Customizer for WooCommerce <= 1.0.6 - Subscriber+ Arbitrary Options Update

> Authenticated users can update arbitrary WordPress options due to missing authorization checks in the Make Email Customizer plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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:** 11 Nov 2025
- **Updated:** 2 Apr 2026
- **Also known as:** GHSA-vfrf-j3pc-4c2g

## What is CVE-2025-11237?

CVE-2025-11237 is a medium-severity missing authorization vulnerability in Unknown Make Email Customizer for WooCommerce, published on 11 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Make Email Customizer for WooCommerce WordPress plugin through 1.0.6 lacks proper authorization checks and option validation in its AJAX actions, allowing any authenticated user, such as a Subscriber, to update arbitrary WordPress options.

## Which versions are affected by CVE-2025-11237?


## How do I fix CVE-2025-11237?

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

## Is CVE-2025-11237 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-11237 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-11237 and fix it if it is affected.

What it is: CVE-2025-11237 is a medium-severity missing authorization vulnerability in Unknown Make Email Customizer for WooCommerce, published on 11 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-11237 exists.

Affected product: Unknown Make Email Customizer for WooCommerce. 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-2025-11237/ (Markdown: https://insights.sbomify.com/CVE-2025-11237/index.md)
```

## Sources

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

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