# CVE-2026-22202: wpDiscuz before 7.6.47 - Destructive GET Action Deletes All Comments by Email

> Attackers can force users to delete all comments associated with their email address via a crafted GET request in wpDiscuz.

- **Severity:** Medium 6.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** 13 Mar 2026
- **Updated:** 13 Mar 2026
- **Also known as:** GHSA-fprc-m8hw-hvjj

## What is CVE-2026-22202?

CVE-2026-22202 is a medium-severity vulnerability in gVectors wpDiscuz, published on 13 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

wpDiscuz before 7.6.47 contains a cross-site request forgery vulnerability that allows attackers to delete all comments associated with an email address by crafting a malicious GET request with a valid HMAC key. Attackers can embed the deletecomments action URL in image tags or other resources to trigger permanent deletion of comments without user confirmation or POST-based CSRF protection.

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

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

It affects 1 product.


Products: Gvectors Wpdiscuz.

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

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

## Is CVE-2026-22202 being exploited?

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

## Other vulnerabilities in gVectors wpDiscuz

- [CVE-2020-24186](https://insights.sbomify.com/CVE-2020-24186/): File upload in n/a (critical 10.0)
- [CVE-2024-9488](https://insights.sbomify.com/CVE-2024-9488/): Comments – wpDiscuz <= 7.6.24 - Authentication Bypass via WordPress.com OAuth provider (critical 9.8)
- [CVE-2020-13640](https://insights.sbomify.com/CVE-2020-13640/): SQL injection in n/a (critical 9.8)
- [CVE-2026-22193](https://insights.sbomify.com/CVE-2026-22193/): wpDiscuz before 7.6.47 - SQL Injection in getAllSubscriptions() (critical 9.2)
- [CVE-2026-22192](https://insights.sbomify.com/CVE-2026-22192/): Voltronic Power SNMP Web Pro 1.1 Authentication Bypass via localStorage (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-22202 is a medium-severity vulnerability in gVectors wpDiscuz, published on 13 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-22202 in the wild and no public exploit code.

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

## Sources

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

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