Paid Memberships Pro – Restrict Member Access to Content, Courses, Communities – Free or Paid Subscriptions <= 2.5.2 - IDOR to Sensitive Information Disclosure

2021-01-06 00:00
Anonymous

Strategic Overview

Status
Patched in 2.5.3
Affected Plugin
Paid Memberships Pro – Content Restriction, User Registration, & Paid Subscriptions
Affected Version
< 2.5.3
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE pending
View all Paid Memberships Pro – Content Restriction, User Registration, & Paid Subscriptions vulnerabilities

At a glance

This record tracks a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Paid Memberships Pro WordPress plugin, affecting versions < 2.5.3. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The issue is fixed in version 2.5.3; sites on affected versions should update now. Disclosed January 2021.

Vulnerability Overview

The Paid Memberships Pro – Restrict Member Access to Content, Courses, Communities – Free or Paid Subscriptions plugin for WordPress is vulnerable to sensitive information disclosure due to incorrect user validation and capabiltiy checking on the pmpro_get_order_json() function that made it possible for attackers to download order data for other users in versions up to, and including 2.5.2.

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 < 2.5.3 carries this weakness at pmpro_get_order_json(), and reaching it takes a caller who can reach the endpoint. 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 the fix is 2.5.3: builds < 2.5.3 are affected, anything from 2.5.3 onward is not.

Remediation

Update to version 2.5.3, 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 2.5.3 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/0eb90948-b2b6-4e30-b903-95b7bce5d734

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C