What this page helps you verify fast
This hub clusters tracked records for 404 to 301 – Redirect Manager, 404 Error Logs & Notifications so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.
Review known vulnerability records for the WordPress plugin 404 to 301 – Redirect Manager, 404 Error Logs & Notifications (`404-to-301`), including severity, CVE references, affected versions, and patch status.
Recent tracked CVEs on this page include CVE-2021-24766 and CVE-2021-4338, so operators can jump from disclosure to patch validation without scanning the full feed first.
Pair this plugin vulnerability hub with practical WordPress hardening, scanner, and patch workflow guidance.
Review patch cadence, privileged access, XML-RPC exposure, backups, and monitoring controls.
Use ownership, update testing, least privilege, and removal criteria to reduce plugin risk.
Compare scanner coverage for plugin CVEs, version detection, alert noise, and remediation workflow.
Use the hub as a decision layer before opening individual records: confirm whether the issue has a CVE, whether a fixed version exists, and whether the affected range overlaps production installs.
Affected range: Versions before 2.0.3. Fixed version: 2.0.3.
Affected range: Versions before 3.0.9. Fixed version: 3.0.9.
Affected range: Versions up to 3.0.7. Fixed version: 3.0.8.
Start with the highest-signal CVE records for this WordPress plugin before scanning the full vulnerability feed.
| Tracked CVE | Issue Type | Affected Versions | Fixed Version | CVSS |
|---|---|---|---|---|
|
CVE-2015-9323
404 to 301 – Redirect, Log and Notify 404 Errors <= 2.0.2 - SQL Injection
|
SQL Injection | Versions before 2.0.3 | 2.0.3 | CVSS 9.8 |
|
CVE-2021-24766
404 to 301 <= 3.0.8 - Logs Deletion via Cross-Site Request Forgery
|
Cross-Site Request Forgery | Versions before 3.0.9 | 3.0.9 | CVSS 6.5 |
|
CVE-2021-4338
404 to 301 <= 3.0.7 - Missing Authorization to Redirect Creation
|
Authorization Bypass | Versions up to 3.0.7 | 3.0.8 | CVSS 6.4 |
404 to 301 – Redirect, Log and Notify 404 Errors <= 2.0.2 - SQL Injection
404 to 301 <= 3.0.8 - Logs Deletion via Cross-Site Request Forgery
404 to 301 <= 3.0.7 - Missing Authorization to Redirect Creation
This hub clusters tracked records for 404 to 301 – Redirect Manager, 404 Error Logs & Notifications so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.
These recent records surface the CVE strings, patch cues, and direct report links most operators need first.
The 404 to 301 – Redirect, Log and Notify 404 Errors plugin for WordPress is vulnerable to Reflected Cross-Site Scripting due to the use of add_query_arg without appropriate escaping on the...
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 ad...
The 404 to 301 plugin for WordPress is vulnerable to authorization bypass due to missing capability checks on the open_redirect & save_redirect functions in versions up to, and including, 3....
Sorted by latest disclosure date so newly published issues surface first.
The 404 to 301 – Redirect, Log and Notify 404 Errors plugin for WordPress is vulnerable to Reflected Cross-Site Scripting due to the use of add_query_arg without appropriate escaping on the URL in versions up to, and including, 3.1.1. This makes it possible for unauthenticated at...
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
The 404 to 301 plugin for WordPress is vulnerable to authorization bypass due to missing capability checks on the open_redirect & save_redirect functions in versions up to, and including, 3.0.7. This makes it possible for authenticated attackers to view, create and edit redirecti...
The 404 to 301 plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'Referer' and 'User-Agent' HTTP Headers in versions before 2.3.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arb...
The 404-to-301 plugin before 2.0.3 for WordPress has SQL injection via the 'orderby' and 'order' parameters.