ProfilePress <= 4.16.12 - Missing Authorization to Authenticated (Subscriber+) Inactive Membership Plan Subscription
Strategic Overview
- Status
- Patched in 4.16.13
- Affected Plugin
- Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content – ProfilePress
- Affected Version
<= 4.16.12- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-4949
At a glance
CVE-2026-4949 is a medium-severity Missing Authorization vulnerability in the Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content WordPress plugin, affecting versions <= 4.16.12. 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.13; sites on affected versions should update now. Disclosed April 2026, reported by Supakiad S. (m3ez).
Vulnerability Overview
The Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content – ProfilePress plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 4.16.12. This is due to the 'process_checkout' function not properly enforcing the plan active status check when a 'change_plan_sub_id' parameter is provided. This makes it possible for authenticated attackers, with Subscriber-level access and above, to subscribe to inactive membership plans by supplying an arbitrary 'change_plan_sub_id' value in the checkout request.
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-862: Missing Authorization
Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content <= 4.16.12 carries this weakness at process_checkout, and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content the fix is 4.16.13: builds <= 4.16.12 are affected, anything from 4.16.13 onward is not.
Remediation
Update to version 4.16.13, 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.13 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 - 8.1CVE-2026-3453: ProfilePress IDOR
CVE-2026-3453 - 7.3CVE-2023-41954: ProfilePress <= 4.13.1 Limited Privilege Escalation
CVE-2023-41954
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C