Paid Memberships Pro <= 2.12.7 - Cross-Site Request Forgery to Level Orders Update
Strategic Overview
- Status
- Patched in 2.12.8
- Affected Version
<= 2.12.7- CVSS
- 5.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2024-0624
At a glance
CVE-2024-0624 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Paid Memberships Pro WordPress plugin, affecting versions <= 2.12.7. 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 2.12.8; sites on affected versions should update now. Disclosed January 2024, reported by kodaichodai.
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, 2.12.7. This is due to missing or incorrect nonce validation on the pmpro_update_level_order() function. This makes it possible for unauthenticated attackers to update the order of 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 <= 2.12.7 carries this weakness at pmpro_update_level_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 2.12.8: builds <= 2.12.7 are affected, anything from 2.12.8 onward is not.
Remediation
Update to version 2.12.8, 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 2.12.8 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Paid Memberships Pro – Content Restriction, User Registration, & Paid Subscriptions
- 9.8CVE-2023-23488: Paid Memberships Pro < 2.9.8 SQL Injection
CVE-2023-23488 - 9.8CVE-2021-25114: Paid Memberships Pro <= 2.6.6 SQL Injection
CVE-2021-25114 - 9.1CVE-2024-37486: Paid Memberships Pro <= 3.0.5 SQL Injection
CVE-2024-37486 - 8.8CVE-2021-20678: Paid Memberships Pro <= 2.5.5 SQL Injection
CVE-2021-20678 - 7.7CVE-2023-0631: Paid Memberships Pro <= 2.9.11 SQL Injection
CVE-2023-0631 - 7.5CVE-2023-6187: Paid Memberships Pro <= 2.12.3 Arbitrary File Upload
CVE-2023-6187 - 7.5CVE-2014-8801: Paid Memberships Pro < 1.7.15 Directory Traversal
CVE-2014-8801 - 7.2Paid Memberships Pro <= 2.0.5 Open Redirect
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C