301 Redirects - Easy Redirect Manager <= 2.40 - Missing Authorization
Strategic Overview
- Status
- Patched in 2.45
- Affected Plugin
- 301 Redirects – Redirect Manager
- Affected Version
<= 2.40- CVSS
- 6.5Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2019-19915
At a glance
CVE-2019-19915 is a medium-severity Missing Authorization vulnerability in the 301 Redirects WordPress plugin, affecting versions <= 2.40. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 2.45; sites on affected versions should update now. Disclosed December 2019, reported by Chloe Chamberland.
Vulnerability Overview
The "301 Redirects - Easy Redirect Manager" plugin before 2.45 for WordPress allows users (with subscriber or greater access) to modify, delete, or inject redirect rules, and exploit XSS, with the /admin-ajax.php?action=eps_redirect_save and /admin-ajax.php?action=eps_redirect_delete actions. This could result in a loss of site availability, malicious redirects, and user infections. This could also be exploited via CSRF.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed.
CWE-862: Missing Authorization
Reaching this weakness in 301 Redirects <= 2.40 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For 301 Redirects the fix is 2.45: builds <= 2.40 are affected, anything from 2.45 onward is not.
Remediation
Update to version 2.45, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: 301 Redirects 2.45 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in 301 Redirects – Redirect Manager
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C