301 Redirects - Easy Redirect Manager <= 2.72 - Cross-Site Request Forgery via dismiss_notice
Strategic Overview
- Status
- Patched in 2.73
- Affected Plugin
- 301 Redirects – Redirect Manager
- Affected Version
<= 2.72- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE pending
At a glance
This record tracks a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the 301 Redirects WordPress plugin, affecting versions <= 2.72. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.73; sites on affected versions should update now. Disclosed March 2023.
Vulnerability Overview
The 301 Redirects - Easy Redirect Manager plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.73. This is due to missing or incorrect nonce validation on the 'dismiss_notice' function. This makes it possible for unauthenticated attackers to dismiss the plugin's admin notifications via forged request granted they can trick a site administrator into performing an action such as clicking on a link.
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 privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
301 Redirects <= 2.72 carries this weakness at dismiss_notice, and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For 301 Redirects the fix is 2.73: builds <= 2.72 are affected, anything from 2.73 onward is not.
Remediation
Update to version 2.73, 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.73 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