Paid Member Subscriptions <= 3.0.6 - Insecure Direct Object Reference to Authenticated (Subscriber+) Payment Data Disclosure
Strategic Overview
- Status
- Patched in 3.0.7
- Affected Plugin
- Paid Membership Subscriptions – Effortless Memberships, Recurring Payments & Content Restriction
- Affected Version
<= 3.0.6- CVSS
- 4.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2026-14847
At a glance
CVE-2026-14847 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Paid Membership Subscriptions WordPress plugin, affecting versions <= 3.0.6. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 3.0.7; sites on affected versions should update now. Disclosed July 2026, reported by WEI HSIANG WANG.
Vulnerability Overview
The Paid Member Subscriptions plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 3.0.6. This is due to missing capability check and nonce verification on the ajax_render_modal_payment_refund function, allowing any authenticated user to query payment records by ID. This makes it possible for authenticated attackers, with subscriber-level access and above, to access payment data belonging to other users by supplying arbitrary payment IDs to the payment refund modal AJAX endpoint.
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
Reaching this weakness in Paid Membership Subscriptions <= 3.0.6 takes an account at Subscriber 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 Membership Subscriptions the fix is 3.0.7: builds <= 3.0.6 are affected, anything from 3.0.7 onward is not.
Remediation
Update to version 3.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 Membership Subscriptions 3.0.7 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Paid Membership Subscriptions – Effortless Memberships, Recurring Payments & Content Restriction
- 9.8CVE-2024-12919: Paid Membership Subscriptions Authentication Bypass
CVE-2024-12919 - 8.8CVE-2021-24728: Membership & Content Restriction SQL Injection
CVE-2021-24728 - 8.1CVE-2025-54017: Paid Membership Subscriptions <= 2.15.5 LFI
CVE-2025-54017 - 8.1CVE-2025-54017: Paid Membership Subscriptions <= 2.15.5 LFI
CVE-2025-54017 - 7.5CVE-2025-49870: Paid Member Subscriptions <= 2.15.1 SQL Injection
CVE-2025-49870 - 7.3CVE-2024-10261: Paid Membership… Arbitrary Shortcode Execution
CVE-2024-10261 - 6.5CVE-2026-105317: Paid Membership Subscriptions SQL Injection
CVE-2026-105317 - 6.4CVE-2025-31088: Paid Member Subscriptions <= 2.14.3 Stored XSS
CVE-2025-31088
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C