# CVE-2026-106608: WordPress WooCommerce plugin 9.8.0-11.1.2 - Shop Manager+ Privilege Escalation vulnerability

> Attackers can escalate privileges due to incorrect privilege assignment in the WooCommerce plugin, requiring an upgrade to secure the site.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Oct 2026
- **Updated:** 11 Oct 2026
- **Also known as:** GHSA-m8vc-mf6h-mr98

## What is CVE-2026-106608?

CVE-2026-106608 is a high-severity vulnerability in Automattic WooCommerce, published on 10 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Incorrect Privilege Assignment vulnerability in Automattic WooCommerce woocommerce allows Privilege Escalation.This issue affects WooCommerce: from 9.8.0 through 11.1.2.

Weakness: CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2026-106608 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-106608 is a high-severity vulnerability in Automattic WooCommerce, published on 10 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-106608 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-106608/ (Markdown: https://insights.sbomify.com/CVE-2026-106608/index.md)
```

## Sources

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

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