CVE-2024-1279

Paid Memberships Pro <= 2.12.8 - Authenticated (Contributor+) Information Disclosure via Shortcode

2024-02-16 00:00
Scott Kingsley Clark

Strategic Overview

Status
Patched in 2.12.9
Affected Version
<= 2.12.8
CVSS
4.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2024-1279
View all Paid Memberships Pro – Content Restriction, User Registration, & Paid Subscriptions vulnerabilities

At a glance

CVE-2024-1279 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Paid Memberships Pro WordPress plugin, affecting versions <= 2.12.8. 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 2.12.9; sites on affected versions should update now. Disclosed February 2024, reported by Scott Kingsley Clark.

Vulnerability Overview

The Paid Memberships Pro – Content Restriction, User Registration, & Paid Subscriptions plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.12.8. This makes it possible for authenticated attackers, with contributor-level access and above, to extract user meta data utilizing the pmpro_member shortcode.

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-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in Paid Memberships Pro <= 2.12.8 takes an account at Contributor level or above. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Paid Memberships Pro the fix is 2.12.9: builds <= 2.12.8 are affected, anything from 2.12.9 onward is not.

Remediation

Update to version 2.12.9, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: Paid Memberships Pro 2.12.9 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

Related records

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