# CVE-2020-36505: Delete All Comments Easily <= 1.3 - All Comments Deletion via CSRF

> An unauthenticated attacker can trick a logged-in admin into deleting all blog comments via CSRF in the Delete All Comments Easily plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A: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:** 1 Nov 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-cvg2-rcw5-j6vm

## What is CVE-2020-36505?

CVE-2020-36505 is a medium-severity vulnerability in Unknown Delete All Comments Easily, published on 1 Nov 2021. 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

The Delete All Comments Easily WordPress plugin through 1.3 is lacking Cross-Site Request Forgery (CSRF) checks, which could result in an unauthenticated attacker making a logged in admin delete all comments from the blog.

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

## Which versions are affected by CVE-2020-36505?

It affects 1 product.


Products: Delete All Comments Easily Project Delete All Comments Easily.

## How do I fix CVE-2020-36505?

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

## Is CVE-2020-36505 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-36505 and fix it if it is affected.

What it is: CVE-2020-36505 is a medium-severity vulnerability in Unknown Delete All Comments Easily, published on 1 Nov 2021. 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-2020-36505 in the wild and no public exploit code.

Affected product: Unknown Delete All Comments Easily. 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-2020-36505/ (Markdown: https://insights.sbomify.com/CVE-2020-36505/index.md)
```

## Sources

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

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