Paid Memberships Pro - Membership Maps Add On < 0.7 - Authenticated (contributor+) Information Disclosure
Strategic Overview
- Status
- Patched in 0.7
- Affected Plugin
- Paid Memberships Pro - Membership Maps Add On
- Affected Version
< 0.7- CVSS
- 4.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2024-1286
At a glance
CVE-2024-1286 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Paid Memberships Pro - Membership Maps Add On WordPress plugin, affecting versions < 0.7. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at contributor level or above. The issue is fixed in version 0.7; sites on affected versions should update now. Disclosed August 2024, reported by Scott Kingsley Clark.
Vulnerability Overview
The Paid Memberships Pro - Membership Maps Add On plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to 0.7 (exclusive) through the 'pmpro_membership_maps' shortcode. This makes it possible for authenticated attackers, with Ccntributor-level access and above, to extract sensitive user meta data.
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 interaction from a victim user.
CWE-639: Authorization Bypass Through User-Controlled Key
Paid Memberships Pro - Membership Maps Add On < 0.7 carries this weakness at pmpro_membership_maps, and reaching it takes an account at contributor level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Paid Memberships Pro - Membership Maps Add On the fix is 0.7: builds < 0.7 are affected, anything from 0.7 onward is not.
Remediation
Update to version 0.7, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Paid Memberships Pro - Membership Maps Add On 0.7 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C