plugin
26 known security issues reported for the 404 To 301 WordPress plugin. Most recent disclosed Jul 18, 2023.
Running 404 To 301 on your site? Check whether your installed version is affected.
Scan your site freeThe Freemius SDK for WordPress is vulnerable to Reflected Cross-Site Scripting via the ‘fs_request_get’ function in versions up to, and including, 2.5.9 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute...
[en] 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 redirections.
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 attackers to inject arbitrary web scripts...
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 attackers to inject arbitrary web scripts...
Reflected Cross-Site Scripting (XSS) vulnerability discovered by WPScanTeam in WordPress 404 to 301 plugin (versions <= 3.1.1). Update the WordPress 404 to 301 plugin to the latest available version (at least 3.1.2).
[en] 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 – 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 redirections.
Broken Access Control vulnerability discovered by Jerome Bruandet (NinTechNet) in WordPress 404 to 301 plugin (versions <= 3.0.7).
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 redirections.
[en] The 404-to-301 plugin before 2.0.3 for WordPress has SQL injection.
Authenticated Option Update vulnerability (Fremius Library security issue) found in WordPress 404 to 301 plugin (versions <= 3.0.1).
The Freemius SDK for WordPress is vulnerable to authorization bypass due to a missing capability check on the _get_db_option and _set_db_option functions in versions up to, and including, 2.2.3. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to change site settings and...
The Freemius SDK for WordPress is vulnerable to authorization bypass due to a missing capability check on the _get_db_option and _set_db_option functions in versions up to, and including, 2.2.3. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to change site settings and...
This plugin is prone to a cross site scripting vulnerability. Update the plugin.
In the file /public/class-404-to-301-public.php the refer input is not sanitized. Update the plugin.
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 arbitrary web scripts in pages that will ex...
Because of this vulnerability, the attackers can inject arbitrary JavaScript or HTML code. Update this plugin.
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 arbitrary web scripts in pages that will ex...
The 404-to-301 plugin before 2.0.3 for WordPress has SQL injection via the 'orderby' and 'order' parameters.
Because of this vulnerability, authenticated administrators can execute arbitrary SQL commands. Update the plugin.
The plugin does not escape some URLs before outputting them back in attributes, leading to Reflected Cross-Site Scripting
The library, used in numerous plugins, does not have proper authorisation when updating blog options, allowing any authenticated users, such as subscriber to update arbitrary options
The 404 to 301 WordPress plugin was found to be affected by a Broken Access Control vulnerability, which could allow malicious redirects or aid in phishing.
There is a stored XSS in the 404-to-301 WP plugin < 2.3.1. Unauthenticated users can visit a specially crafted URL and the redirect path will be logged to the database. The redirection source is stored unescaped in the database, thus it is served as-is and evaluated in the browsers of logged-in admins when they chec...
** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided.
Run a free security scan to detect vulnerable plugins and themes, exposed files, and malware — no plugin install, no signup.
Scan your site free