# CVE-2026-92437: Mailchimp for WooCommerce < 6.3 - Unauthenticated Abandoned Cart Modification and Deletion

> Unauthenticated attackers can modify or delete other customers' abandoned cart records due to missing authorization checks in the Mailchimp for WooCommerce plugin.

- **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:** 3 Oct 2026
- **Updated:** 3 Oct 2026
- **Also known as:** GHSA-g66g-hh39-fx5j

## What is CVE-2026-92437?

CVE-2026-92437 is a medium-severity missing authorization vulnerability in Unknown Mailchimp for WooCommerce, published on 3 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Mailchimp for WooCommerce WordPress plugin before 6.3 does not require authentication, a nonce or an ownership check before it acts on a customer's abandoned-cart record identified from request-supplied data, allowing an unauthenticated attacker to modify or delete another customer's stored cart.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-92437 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92437 is a medium-severity missing authorization vulnerability in Unknown Mailchimp for WooCommerce, published on 3 Oct 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-92437 in the wild and no public exploit code.

Affected product: Unknown Mailchimp 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-2026-92437/ (Markdown: https://insights.sbomify.com/CVE-2026-92437/index.md)
```

## Sources

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

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