CVE-2024-3215

Paid Memberships Pro <= 3.0.1 - Cross-Site Request Forgery

2024-04-15 00:00
Whit Taylor

Strategic Overview

Status
Patched in 3.0.2
Affected Version
<= 3.0.1
CVSS
5.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-3215
View all Paid Memberships Pro – Content Restriction, User Registration, & Paid Subscriptions vulnerabilities

At a glance

CVE-2024-3215 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Paid Memberships Pro WordPress plugin, affecting versions <= 3.0.1. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.0.2; sites on affected versions should update now. Disclosed April 2024, reported by Whit Taylor.

Vulnerability Overview

The Paid Memberships Pro – Content Restriction, User Registration, & Paid Subscriptions plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.0.1. This is due to missing or incorrect nonce validation on the pmpro_update_level_group_order() function. This makes it possible for unauthenticated attackers to update order levels 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, and no interaction from a victim user.

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

Paid Memberships Pro <= 3.0.1 carries this weakness at pmpro_update_level_group_order(), 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 Paid Memberships Pro the fix is 3.0.2: builds <= 3.0.1 are affected, anything from 3.0.2 onward is not.

Remediation

Update to version 3.0.2, or a newer patched version

How does WordSec protect against this?

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