# CVE-2026-48888: WordPress WooCommerce plugin < 11.1.0 - Denial of Service Attack vulnerability

> An attacker can cause a denial of service in WordPress sites using the WooCommerce plugin by exploiting resource allocation flaws.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Sep 2026
- **Updated:** 8 Sep 2026
- **Also known as:** GHSA-p55m-mp38-r6cw

## What is CVE-2026-48888?

CVE-2026-48888 is a high-severity denial of service vulnerability in Automattic WooCommerce, published on 8 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Allocation of Resources Without Limits or Throttling vulnerability in Automattic WooCommerce allows HTTP DoS.

This issue affects WooCommerce: from n/a before 11.1.0.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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


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

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

## Is CVE-2026-48888 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-48888 is a high-severity denial of service vulnerability in Automattic WooCommerce, published on 8 Sep 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-48888 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-48888/ (Markdown: https://insights.sbomify.com/CVE-2026-48888/index.md)
```

## Sources

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

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