# CVE-2021-24766: 404 to 301 < 3.0.9 - Logs Deletion via CSRF

> A CSRF vulnerability in the 404 to 301 WordPress plugin allows attackers to force logged-in admins to delete all 404 error logs.

- **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:** 8 Nov 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-h33c-59r7-5m89

## What is CVE-2021-24766?

CVE-2021-24766 is a medium-severity vulnerability in Unknown 404 to 301 – Redirect, Log and Notify 404 Errors, published on 8 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 404 to 301 – Redirect, Log and Notify 404 Errors WordPress plugin before 3.0.9 does not have CSRF check in place when cleaning the logs, which could allow attacker to make a logged in admin delete all of them via a CSRF attack

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

## Which versions are affected by CVE-2021-24766?

It affects 1 product.


Products: 404 to 301 Project 404 to 301.

## How do I fix CVE-2021-24766?

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

## Is CVE-2021-24766 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-24766 and fix it if it is affected.

What it is: CVE-2021-24766 is a medium-severity vulnerability in Unknown 404 to 301 – Redirect, Log and Notify 404 Errors, published on 8 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-2021-24766 in the wild and no public exploit code.

Affected product: Unknown 404 to 301 – Redirect, Log and Notify 404 Errors. 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-2021-24766/ (Markdown: https://insights.sbomify.com/CVE-2021-24766/index.md)
```

## Sources

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

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