CVE-2023-1331

Redirection <= 1.1.4 - Cross-Site Request Forgery to Plugin Reset

2023-03-21 00:00
Mohamed Selim

Strategic Overview

Status
Patched in 1.1.5
Affected Plugin
Redirection
Affected Version
<= 1.1.4
CVSS
5.4Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-1331
View all Redirection vulnerabilities

At a glance

CVE-2023-1331 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Redirection WordPress plugin, affecting versions <= 1.1.4. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.1.5; sites on affected versions should update now. Disclosed March 2023, reported by Mohamed Selim.

Vulnerability Overview

The Redirection plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.1.4. This is due to missing or incorrect nonce validation on the 'uninstall' function hooked via admin_post. This makes it possible for unauthenticated attackers to deactivate and reset the plugin 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.

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

Redirection <= 1.1.4 carries this weakness at uninstall, 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 Redirection the fix is 1.1.5: builds <= 1.1.4 are affected, anything from 1.1.5 onward is not.

Remediation

Update to version 1.1.5, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Redirection: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Redirection 1.1.5 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