# CVE-2026-88828: Blacklist Manager for WooCommerce 1.3.0 - 2.3.1 - Blocked User Restriction Bypass via XML-RPC and Application Passwords

> Blocked users can bypass restrictions and authenticate via XML-RPC or Application Passwords in the Blacklist Manager for WooCommerce plugin.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Sep 2026
- **Updated:** 28 Sep 2026
- **Also known as:** GHSA-gg4x-5759-6rq2

## What is CVE-2026-88828?

CVE-2026-88828 is a medium-severity authentication bypass vulnerability in Unknown Blacklist Manager, published on 28 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Blacklist Manager for WooCommerce WordPress plugin from 1.3.0 to 2.3.1 does not enforce its user blocking on every authentication path, allowing the holder of an account the site owner has blocked to keep authenticating with that account's privileges, without the block being enforced or recorded.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

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


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

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

## Is CVE-2026-88828 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-88828 is a medium-severity authentication bypass vulnerability in Unknown Blacklist Manager, published on 28 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-88828 in the wild and no public exploit code.

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

## Sources

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

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