Redirection vulnerability records and what to read in the plugin's rules and logs
Redirection has one free edition and, unless configured otherwise, logs every redirect and 404 on a site.
This page reads its vulnerability records, then shows where to check its redirect rules, log settings, import and export permissions and REST API access.
On this page
Redirection vulnerability history
Source: Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . It lists 5 records for Redirection. Copyright notices, licence terms and a link to each source record are under Data source and licence at the foot of this page.
Update to at least version 3.6.4
Worked out from data retrieved on .
Every affected range listed in this source for Redirection ends before version 3.6.4.
A vendor can publish a security release before this source records it. Read the plugin's own changelog as well as this history.
Redirection <= 3.6.3 - Cross-Site Request Forgery to Remote Code Execution
- Published:
- Last updated:
- Severity:
- High (CVSS 8.8)
Affected versions- All versions up to and including 3.6.3
Patched versions: 3.6.4
Update to at least version 3.6.4.
Redirection <= 2.7.3 - Local File Inclusion
- Published:
- Last updated:
- Severity:
- High (CVSS 7.2)
- CVE:
- CVE-2018-1000504
Affected versions- All versions up to and including 2.7.3
Patched versions: 2.8
Update to at least version 2.8.
Redirection <= 2.2.8 - Reflected Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.1)
- CVE:
- CVE-2011-5329
Affected versions- All versions before 2.2.9
Patched versions: 2.2.9
Update to at least version 2.2.9.
Redirection <= 2.2.9 - Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.3)
- CVE:
- CVE-2011-4562
Affected versions- All versions before 2.2.10
Patched versions: 2.2.10
Update to at least version 2.2.10.
Redirection < 2.2.12 - Reflected Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.1)
- CVE:
- CVE-2012-6717
Affected versions- All versions before 2.2.12
Patched versions: 2.2.12
Update to at least version 2.2.12.
Check Redirection on a live site
Read-only checks for a site you own or are authorised to review. Each step uses the WordPress dashboard or WP-CLI and sends no test payloads to the site.
Where Redirection takes input
Redirection is a redirect manager published on WordPress.org by John Godley.
Its listing describes managing 301 redirections and keeping track of 404 errors, and says there is no premium version. So a Redirection vulnerability check has one edition to match.
Signed-in users work at Tools > Redirection, where the vendor's getting started page describes a top menu. Who may open it depends on one capability: the permissions page says a redirection_role filter returns it and defaults to manage_options, "ensuring only administrators can access the plugin", and shows site code changing that default.
Input also arrives without that screen. The options page says Redirection can monitor URL changes to posts, pages and custom post types and auto-create a redirect from the old post URL to the new one. It also says the plugin will log every redirect and every 404 unless configured otherwise, and the logs page lists what the logs contain about a visitor, including the URL visited, the browser agent, the IP address and, when available, the referrer.
Reading the Redirection plugin vulnerabilities on record
Cross-site scripting is wording that recurs in the titles of the Redirection records named here.
None of these titles carries wording about a role or a login, so they do not settle who could reach each flaw.
- A record published on 14 Nov 2018 without a CVE id has a title ending "Cross-Site Request Forgery to Remote Code Execution". Affected: all versions up to and including 3.6.3. Patched versions: 3.6.4.
- CVE-2018-1000504 has a title ending "Local File Inclusion". Affected: all versions up to and including 2.7.3. Patched versions: 2.8.
- CVE-2011-5329 has a title ending "Reflected Cross-Site Scripting". Affected: all versions before 2.2.9. Patched versions: 2.2.9.
- CVE-2012-6717 has a title that also ends "Reflected Cross-Site Scripting". Affected: all versions before 2.2.12. Patched versions: 2.2.12.
Titles and version fields
Match a site on the version fields, not on a title. CVE-2011-5329 has a title beginning "Redirection <= 2.2.8" while its affected field reads all versions before 2.2.9, and CVE-2011-4562, whose title ends "Cross-Site Scripting", pairs "Redirection <= 2.2.9" with an affected field of all versions before 2.2.10 and a patched versions field of 2.2.10.
For CVE-2018-1000504 the affected range ends at 2.7.3 and the patched versions field lists 2.8: the fields say nothing about the versions between the two, so 2.8 is the one to reach for that record.
Where to read each Redirection check
Work through the checklist on this page as an administrator on a site you are authorised to review, reading and saving nothing.
One caution first: the options page says a new version may sometimes need to alter the redirect database, and that with the Data Upgrade option set to automatic, any visit to the admin interface performs the upgrade. So after an update, use a staging copy or ask whoever maintains the site before signing in.
The Description column of the Redirection row on the Plugins screen includes the version number; write it down with the date. WordPress displays an update notice there when a plugin hosted in its Plugin Directory has a newer version.
Before relying on the update guidance at the top of the history, also read the changelog on the plugin's WordPress.org listing, where one entry includes the line "Tighten capability checks and improve proxy IP address handling".
Redirects in the top menu opens the table of all redirects. For each, write down the source URL, the target, its group and whether it is enabled. Flag targets on a domain the business does not control, and regular expression rules that copy information from the source URL into the target, which the regular expressions page describes.
The vendor's security page describes an open redirect as one "that uses data supplied by the user to affect the redirect destination", and says most redirects are not affected.
Then read the Site screen. The site options page says its settings include HTTP headers and Relocate Site, which redirects all requests for the site's URLs to the equivalent URL on another domain. On the Groups screen, note any group of the Apache kind.
The groups page says that kind uses the Apache Module option on the options page to save redirects to a .htaccess file, and the options page says that option is where the file's path is configured. Note the path and read that file too.
On the Options screen, record the log expiry for redirects and for 404s, the IP logging level and the additional log options the options page lists: log external redirects, track redirect hits and access date, and capture HTTP header information. Note any IP header other than REMOTE_ADDR and any proxy server IPs specified with it: the page says these header values can be overridden by the client, and that a custom header will only be trusted if REMOTE_ADDR is one of the configured proxy server IP addresses.
The same page describes an RSS Token, a unique key that lets an RSS reader access the logs without a username and password. Record whether that feed address has been shared, and keep the token out of your notes.
On the Log screen, leave an IP address and any Geo Info or Agent Info link unclicked: the privacy page says those lookups send the IP address or user agent to an external service.
The vendor's permissions page describes these as set by filters in code, so this check starts as a search. It lists redirection_cap_io_manage, "ability to perform import/export actions", among the permissions that, in version 4.6 and newer, the redirection_capability_check filter can decide. Search the site's plugin and theme code for that filter and for redirection_role, and look on the Plugins screen for the page's sample plugin, Advanced Redirection Permissions.
Write down the capability each returns. With the default in place, the permissions page says only administrators can access the plugin.
The Administrator filter link on the Users screen lists the accounts with that role. An import can carry more than rules: the import and export page says JSON files support importing of redirects, groups, logs and settings.
The options page says Redirection uses the WordPress REST API to communicate with WordPress, with a REST API option set to Default or to Raw, which goes through /index.php?rest_route=/. Record which. The vendor's REST API reference, which describes itself as not yet exhaustive, groups its routes under redirection/v1 as redirects, groups, logs, 404 logs, settings and import and export, and says all requests must be authenticated.
On a site you are authorised to review, open /wp-json/redirection/v1/redirect in a browser window that is not signed in and record the status that comes back. The reference lists that route's responses as 200 Redirect list, 401 Unauthorized and 404 Route not found.
Leave the plugin's Support page alone, because the options page says that if the REST API setting is changed and something breaks, going there makes Redirection attempt to fix it.
What a Redirection version match cannot show
A version inside an affected range shows that a known record covers the installed copy of Redirection.
It does not show whether the site was attacked, and it says nothing about how this copy is set up: a redirect to a domain nobody recognises, a Relocate Site value, a redirection_role filter that hands the plugin to a lower role, or a log feed address shared with its RSS token.
A WordPress security audit goes further: it calls the REST routes under /wp-json/ without a session, replays requests captured from an administrator's plugin settings screens as a subscriber, and confirms that editors cannot reach plugin or settings requests by calling them directly.
Frequently asked questions
The record published on 14 Nov 2018, which has no CVE id, covers all versions up to and including 3.6.3 and lists 3.6.4 in its patched versions field. CVE-2012-6717 words its range another way, as all versions before 2.2.12, and lists 2.2.12. Read each record's two fields against the version you wrote down, then the update guidance at the top of the history.
Yes, through code. The vendor's permissions page offers a sample plugin, Advanced Redirection Permissions, which it says restricts access to the capability edit_posts (i.e. editors) and, if used on version 4.6 or newer, will only give them access to view and create redirects.
By default, yes. The options page says Redirection collects the full IP address of every redirected URL and 404 error by default, and lists anonymised IP logging and no IP logging as the other options. The vendor's privacy page says nothing is stored externally and all information is stored on your server.
The records are reports matched to version ranges, not a rating of Redirection: CVE-2018-1000504, whose title ends "Local File Inclusion", covers all versions up to and including 2.7.3 and lists 2.8 in its patched versions field. Separately, the vendor's security page names the open redirect as the primary route by which a user of Redirection can inadvertently create a security issue.
Scope the right test for your application
Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.
Data source and licenceHide the data source and licence
The vulnerability records on this page come from Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . The records contain material that is subject to copyright. Each copyright notice and its licence are reproduced once below, followed by a link to every source record.
Copyright 2012-2026 Defiant Inc.
Applies to every record listed below.
Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.
Copyright 1999-2026 The MITRE Corporation
Applies to 4 of the 5 records listed below.
CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.
Source records
- Redirection <= 3.6.3 - Cross-Site Request Forgery to Remote Code Execution
- Redirection <= 2.7.3 - Local File Inclusion (CVE-2018-1000504)
- Redirection <= 2.2.8 - Reflected Cross-Site Scripting (CVE-2011-5329)
- Redirection <= 2.2.9 - Cross-Site Scripting (CVE-2011-4562)
- Redirection < 2.2.12 - Reflected Cross-Site Scripting (CVE-2012-6717)