301 Redirects - Easy Redirect Manager < 2.51 - SQL Injection
Strategic Overview
- Status
- Patched in 2.51
- Affected Plugin
- 301 Redirects – Redirect Manager
- Affected Version
< 2.51- CVSS
- 7.2High
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2021-24142
At a glance
CVE-2021-24142 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the 301 Redirects WordPress plugin, affecting versions < 2.51. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 2.51; sites on affected versions should update now. Disclosed January 2021, reported by Nguyen Van Khanh.
Vulnerability Overview
Unvaludated input in the 301 Redirects - Easy Redirect Manager WordPress plugin, versions before 2.51, did not sanitise its "Redirect From" column when importing a CSV file, allowing high privilege users to perform SQL injections.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Reaching this weakness in 301 Redirects < 2.51 takes a caller who can reach the endpoint. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.
A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For 301 Redirects the fix is 2.51: builds < 2.51 are affected, anything from 2.51 onward is not.
Remediation
Update to version 2.51, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to 301 Redirects: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: 301 Redirects 2.51 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in 301 Redirects – Redirect Manager
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C