# CVE-2026-107791: WP Comment Cleaner 6.1 - 7.1 - Subscriber+ Bulk Comment Deletion via nav_delete_all_comment

> Authenticated subscribers can permanently delete all site comments due to missing capability checks in the WP Comment Cleaner plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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:** 12 Oct 2026
- **Updated:** 12 Oct 2026
- **Also known as:** GHSA-p3pc-rx4j-4w3p

## What is CVE-2026-107791?

CVE-2026-107791 is a medium-severity missing authorization vulnerability in Unknown WP Comment Cleaner, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The WP Comment Cleaner  WordPress plugin before 7.2 does not perform a capability check or validate a nonce on one of its bulk comment-deletion routines, allowing authenticated users with minimal permissions, such as subscribers, to permanently delete all comments on the site.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-107791 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-107791 is a medium-severity missing authorization vulnerability in Unknown WP Comment Cleaner, published on 12 Oct 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-107791 in the wild and no public exploit code.

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

## Sources

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

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