CVE-2021-24766: The 404 to 301 – Redirect, Log and Notify 404 Errors WordPress plugin before 3.0.9 does not have CSRF check in

Q: How do I fix CVE-2021-24766?

404 to 301: upgrade to 3.0.9. Exact commands for each OS are on this page.

Q: Is CVE-2021-24766 being exploited?

CVE-2021-24766 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2021-24766 affect?

CVE-2021-24766 affects 404 to 301. Severity is medium (CVSS 6.5). 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

Q: How urgent is CVE-2021-24766?

Priority 39/100. Public exploit reference

Routine

MEDIUM 6.5UPGRADE

CVE-2021-24766 is a medium-severity flaw (CVSS 6.5) affecting 404 to 301. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.5% (top 54%)
CISA exploited list	No
Weakness	CWE-352
Published	2021-11-08
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: 404 to 301 project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2021-11-08 18:15 UTCPublished CVE record published
2026-06-17 03:40 UTCUpdated Record last modified

404 to 301 project 404 to 301 UPGRADE

Affected: < 3.0.9

Fixed in: 3.0.9

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy 404-to-301 || rpm -q 404-to-301 || 404-to-301 --version

2. UPGRADE to 3.0.9 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade 404-to-301

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade 404-to-301

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2021-24766?

404 to 301: upgrade to 3.0.9. Exact commands for each OS are on this page.

Is CVE-2021-24766 being exploited?

CVE-2021-24766 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2021-24766 affect?

CVE-2021-24766 affects 404 to 301. Severity is medium (CVSS 6.5). 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

How urgent is CVE-2021-24766?

Priority 39/100. Public exploit reference

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2021-4338 MEDIUM 6.4 UPGRADE The 404 to 301 plugin for WordPress is vulnerable to authorization bypass due to missing capability checks on

References

← Back to latest CVEs