ProfilePress <= 4.16.16 - Insecure Direct Object Reference to Authenticated (Subscriber+) Subscription Cancellation
Strategic Overview
- Status
- Patched in 4.16.17
- Affected Plugin
- Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content – ProfilePress
- Affected Version
<= 4.16.16- CVSS
- 4.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2026-10820
At a glance
CVE-2026-10820 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content WordPress plugin, affecting versions <= 4.16.16. 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 4.16.17; sites on affected versions should update now. Disclosed June 2026, reported by Haitam Lazaar.
Vulnerability Overview
The ProfilePress plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 4.16.16. This is due to missing ownership verification on the sub_id parameter before performing subscription actions. This makes it possible for authenticated attackers, with subscriber-level access and above, to cancel arbitrary users' subscriptions by manipulating the subscription ID parameter.
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 Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content <= 4.16.16 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 Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content the fix is 4.16.17: builds <= 4.16.16 are affected, anything from 4.16.17 onward is not.
Remediation
Update to version 4.16.17, 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 Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content 4.16.17 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 Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content – ProfilePress
- 9.8CVE-2026-12497: ProfilePress <= 4.16.17 Privilege Escalation
CVE-2026-12497 - 9.8CVE-2021-34624: ProfilePress 3.0 - 3.1.3 Arbitrary File Upload
CVE-2021-34624 - 9.8CVE-2021-34622: ProfilePress 3.0 - 3.1.3 Privilege Escalation
CVE-2021-34622 - 9.8CVE-2021-34623: User Registration Privilege Escalation
CVE-2021-34623 - 9.8CVE-2021-34621: User Registration Privilege Escalation
CVE-2021-34621 - 8.8CVE-2026-13352: Paid Membership Plugin Limited Unsafe File Upload
CVE-2026-13352 - 7.3CVE-2023-41954: ProfilePress <= 4.13.1 Limited Privilege Escalation
CVE-2023-41954 - 7.2CVE-2022-47444: ProfilePress <= 4.5.3 Cross-Site Scripting
CVE-2022-47444
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C