Simple Membership <= 4.7.5 - Missing Authorization to Unauthenticated Arbitrary Member Account Deactivation via Forged Stripe 'charge.refunded' Webhook
Strategic Overview
- Status
- Patched in 4.7.6
- Affected Plugin
- Simple Membership
- Affected Version
<= 4.7.5- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-12093
At a glance
CVE-2026-12093 is a medium-severity Missing Authorization vulnerability in the Simple Membership WordPress plugin, affecting versions <= 4.7.5. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.7.6; sites on affected versions should update now. Disclosed June 2026, reported by Nikita Fenko.
Vulnerability Overview
The Simple Membership plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 4.7.5. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to deactivate arbitrary member accounts by forging a charge.refunded webhook event containing a victim's subscription ID, setting the target member's account_state to 'inactive' and triggering cancellation hooks, transaction-record status changes, and cancellation notification emails. This vulnerability is exploitable only on installations where no Stripe webhook signing secret has been configured, which is the default out-of-the-box state; sites that have configured the stripe-webhook-signing-secret option are routed to the properly verified HMAC path and are not affected.
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 privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
Simple Membership <= 4.7.5 carries this weakness at inactive, and reaching it takes no account at all. 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 Simple Membership the fix is 4.7.6: builds <= 4.7.5 are affected, anything from 4.7.6 onward is not.
Remediation
Update to version 4.7.6, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Simple Membership 4.7.6 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 Simple Membership
- 9.8CVE-2022-2317: Simple Membership Membership Privilege Escalation
CVE-2022-2317 - 8.8CVE-2023-41956: Simple Membership <= 4.3.4 Account Takeover
CVE-2023-41956 - 8.8CVE-2022-2273: Simple Membership Membership Privilege Escalation
CVE-2022-2273 - 8.8CVE-2022-0328: Simple Membership CSRF to Arbitrary Member Deletion
CVE-2022-0328 - 8.8CVE-2019-14328: Simple Membership <= 3.8.4 Cross-Site Request Forgery
CVE-2019-14328 - 8.8CVE-2016-10884: Simple Membership <= 3.3.2 Multiple CSRF
CVE-2016-10884 - 7.3CVE-2023-41957: Simple Membership <= 4.3.4 Privilege escalation
CVE-2023-41957 - 7.2CVE-2026-42663: Simple Membership <= 4.7.2 Stored Cross-Site Scripting
CVE-2026-42663
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C