CVE-2021-24231

Patreon WordPress <= 1.6.9 - Cross-Site Request Forgery

2021-03-26 00:00
Marc-Alexandre Montpas

Strategic Overview

Status
Patched in 1.7.0
Affected Plugin
Patreon WordPress
Affected Version
<= 1.6.9
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2021-24231
View all Patreon WordPress vulnerabilities

At a glance

CVE-2021-24231 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Patreon WordPress WordPress plugin, affecting versions <= 1.6.9. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.7.0; sites on affected versions should update now. Disclosed March 2021, reported by Marc-Alexandre Montpas.

Vulnerability Overview

The Jetpack Scan team identified a Cross-Site Request Forgery vulnerability in the Patreon WordPress plugin before 1.7.0, allowing attackers to make a logged administrator disconnect the site from Patreon by visiting a specially crafted 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 confidentiality, integrity, availability — full site compromise territory.

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

Reaching this weakness in Patreon WordPress <= 1.6.9 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 Patreon WordPress the fix is 1.7.0: builds <= 1.6.9 are affected, anything from 1.7.0 onward is not.

Remediation

Update to version 1.7.0, or a newer patched version

How does WordSec protect against this?

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