# CVE-2026-3589: WooCommerce < 10.5.3 - Arbitrary Admin User Creation via CSRF

> Unauthenticated attackers can trick admins into creating arbitrary admin users via CSRF, leading to privilege escalation and account takeover.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Mar 2026
- **Updated:** 6 Mar 2026
- **Also known as:** GHSA-2wr3-vxcp-rxmc

## What is CVE-2026-3589?

CVE-2026-3589 is a high-severity vulnerability in Automattic WooCommerce, published on 6 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The WooCommerce WordPress plugin from versions 5.4.0 to 10.5.2 does not properly handle batch requests, which could allow unauthenticated users to make a logged in admin call non store/WC REST endpoints, and create arbitrary admin users via a CSRF attack for example.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2026-3589 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-3589 is a high-severity vulnerability in Automattic WooCommerce, published on 6 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-3589 in the wild and no public exploit code.

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

## Sources

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

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