SEO Redirection Plugin – 301 Redirect Manager <= 7.8 - Cross-Site Request Forgery

2021-09-15 00:00
WPScanTeam

Strategic Overview

Status
Patched in 7.9
Affected Version
<= 7.8
CVSS
6.5Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE pending
View all SEO Redirection Plugin – 301 Redirect Manager vulnerabilities

At a glance

This record tracks a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the SEO Redirection Plugin WordPress plugin, affecting versions <= 7.8. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high availability impact). Exploitation requires no authentication. The issue is fixed in version 7.9; sites on affected versions should update now. Disclosed September 2021, reported by WPScanTeam.

Vulnerability Overview

The SEO Redirection Plugin – 301 Redirect Manager plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 7.8. This is due to missing or incorrect nonce validation. This makes it possible for unauthenticated attackers to delete arbitrary redirects via a 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. A successful exploit has high impact on availability.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in SEO Redirection Plugin <= 7.8 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 SEO Redirection Plugin the fix is 7.9: builds <= 7.8 are affected, anything from 7.9 onward is not.

Remediation

Update to version 7.9, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to SEO Redirection Plugin: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: SEO Redirection Plugin 7.9 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C