HomeWordPress vulnerabilitiesRedirection
Redirection vulnerabilities
Redirection has 5 known vulnerabilities in this database. The most recent published record is dated 17 Apr 2023.
- Known vulnerabilities
- 5
- Active installs
- 2m+
- Latest version
- 5.10.1
- Last updated
- 19 Sep 2026
- Most recent
- 17 Apr 2023
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site request forgery (CSRF) CVE-2023-1331 | Medium 6.5 | Before 1.1.5 | Fixed in 1.1.5 | 17 Apr 2023 |
| Cross-site request forgery (CSRF) CVE-2023-1330 | Medium 6.5 | Before 1.1.4 | Fixed in 1.1.4 | 3 Apr 2023 |
| Cross-site scripting (XSS) CVE-2011-5329 | Medium 6.1 | Before 2.2.9 | Fixed in 2.2.9 | 28 Aug 2019 |
| Cross-site scripting (XSS) CVE-2012-6717 | Medium 6.1 | Before 2.2.12 | Fixed in 2.2.12 | 28 Aug 2019 |
| Cross-site scripting (XSS) CVE-2011-4562 | Not scored | Not yet published | Check for an update | 28 Nov 2011 |
Read the published descriptions
- CVE-2023-1331, 17 Apr 2023
- The Redirection WordPress plugin before 1.1.5 does not have CSRF checks in the uninstall action, which could allow attackers to make logged in admins delete all the redirections through a CSRF attack. CVE record
- CVE-2023-1330, 3 Apr 2023
- The Redirection WordPress plugin before 1.1.4 does not add nonce verification in place when adding the redirect, which could allow attackers to add redirects via a CSRF attack. CVE record
- CVE-2011-5329, 28 Aug 2019
- The redirection plugin before 2.2.9 for WordPress has XSS in the admin menu, a different issue than CVE-2011-4562. CVE record
- CVE-2012-6717, 28 Aug 2019
- The redirection plugin before 2.2.12 for WordPress has XSS, a different issue than CVE-2011-4562. CVE record
- CVE-2011-4562, 28 Nov 2011
- Multiple cross-site scripting (XSS) vulnerabilities in (1) view/admin/log_item.php and (2) view/admin/log_item_details.php in the Redirection plugin 2.2.9 for WordPress allow remote attackers to inject arbitrary web script or HTML via the Referer HTTP header in a request to a post that does not exist. CVE record
What to do if you run Redirection
If you run Redirection, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Redirection vulnerabilities
Free. We email you when a new vulnerability is published for Redirection, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.