CVE-2026-12093 json
Simple Membership <= 4.7.5 - Missing Authorization to Unauthenticated Arbitrary Member Account Deactivation via Forged Stripe 'charge.refunded' Webhook
published 4mo ago modified 4mo ago also EUVD-2026-37847
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 29%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2026-12093 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 4mo ago
Exploit prediction
0.35% chance of exploitation in the next 30 days, higher than 29% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
Affected products
- wpinsider-1 Simple Membership
Classification
- Weakness
-
- CWE-862 Missing Authorization
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/2f91a7c3-ee0e-48e9-aa5f-dfc1160bbc09?source=cve
- plugins.trac.wordpress.org /browser/simple-membership/tags/4.7.4/ipn/swpm-stripe-webhook-handler.php#L297
- plugins.trac.wordpress.org /browser/simple-membership/tags/4.7.4/ipn/swpm-stripe-webhook-handler.php#L71
- plugins.trac.wordpress.org /browser/simple-membership/tags/4.7.4/classes/class.swpm-wp-loaded-tasks.php#L96
- plugins.trac.wordpress.org /browser/simple-membership/tags/4.7.4/ipn/swpm_handle_subsc_ipn.php#L381
- plugins.trac.wordpress.org /browser/simple-membership/tags/4.7.3/ipn/swpm-stripe-webhook-handler.php#L297
- plugins.trac.wordpress.org /browser/simple-membership/tags/4.7.3/ipn/swpm-stripe-webhook-handler.php#L71
- plugins.trac.wordpress.org /browser/simple-membership/tags/4.7.3/classes/class.swpm-wp-loaded-tasks.php#L96
- plugins.trac.wordpress.org /browser/simple-membership/tags/4.7.3/ipn/swpm_handle_subsc_ipn.php#L381
- plugins.trac.wordpress.org /changeset?sfp_email=&sfph_mail=&reponame=&old=3573852%40simple-membership&new=3573852%40simple-membership&sfp
Sources
- CVE List CVE-2026-12093
- NVD CVE-2026-12093
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.