Is 404-to-301 (WordPress plugin) vulnerable?

WordPress 404-to-301 has 3 known advisories in the phpwarden feed. Feed 2026.10.29.1, updated 2026-10-28.

3advisories

1critical

0on CISA KEV

1no fix recorded

CVE	Title	Severity	CVSS	Affected	Fixed in
CVE-2015-9323	The 404-to-301 plugin before 2.0.3 for WordPress has SQL injection.	critical	9.8	`<2.0.3`	`2.0.3`
CVE-2021-4338	The 404 to 301 plugin for WordPress is vulnerable to authorization bypass due to missing capability checks on the open_redirect & save_redir	medium	6.4	`<=3.0.7`	–
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 place when cleaning the logs,	medium	6.5	`<3.0.9`	`3.0.9`

Am I affected?

Find out in one command. phpwarden checks your WordPress install against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# one-time install
pip install phpwarden

# then
phpwarden wordpress /var/www/html

Or keep it checked automatically with the GitHub Action or a nightly cron; see WordPress docs.

Install docs How findings are ranked

A version is vulnerable when it falls inside an affected range and below the fixed version. phpwarden applies these ranges to the exact versions in your lockfile or install, so you only see what applies to you.