404 to 301 Vulnerabilities
The 404 to 301 WordPress plugin has 3 known security vulnerabilities. The most recent was disclosed on June 7, 2022. Check whether your site runs an affected version below.
View 404 to 301 on WordPress.orgSummary
Latest vulnerability disclosed on June 7, 2022.
Recommendation
WPSentry recommends installing with caution
Use 404 to 301 only with care. This plugin has a history of high-severity vulnerabilities — always run the latest version and monitor it for newly disclosed issues.
Is your site affected?
Run a free external scan to detect 404 to 301 and 35+ other WordPress security checks — no login or plugin required.
Known 404 to 301 vulnerabilities
- medium
404 to 301 – Redirect, Log and Notify 404 Errors <= 3.1.1 - Reflected Cross-Site Scripting
Affected versions: <=3.1.1Disclosed June 7, 2022 - high
Freemius SDK <= 2.2.3 - Missing Authorization to Arbitrary Options Update
Affected versions: <3.0.2Disclosed February 25, 2019 - high
404 to 301 <= 2.3.0 - Unauthenticated Stored Cross-Site Scripting
Affected versions: <=2.3.0Disclosed August 27, 2016
How to stay protected
Update promptly
Keep 404 to 301 on its latest release — most vulnerabilities are fixed in newer versions.
Scan regularly
Run an external scan after every update to catch outdated or vulnerable software early.
Monitor continuously
Enable monitoring to get alerted the moment a new issue affects your stack.