CVE-2026-15414 Privilege escalation in Subscriptions for WooCommerce
Authenticated contributors can escalate to Administrator by manipulating membership plan metadata if the Pro companion plugin is active.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-15414?
CVE-2026-15414 is a high-severity vulnerability in wpswings Subscriptions for WooCommerce, published on 1 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
The Subscriptions for WooCommerce plugin for WordPress is vulnerable to Privilege Escalation in versions up to, and including, 2.0.0. This is due to the `save_meta_boxes()` function persisting the `_wps_plan_user_role` membership plan meta from `$_POST` without an allowlist that excludes privileged roles — the only validations applied, `sanitize_key()` and `wp_roles()->is_role()`, both accept `'administrator'` as a valid value, and the UI's `disabled` attribute on the role dropdown is a client-side-only control trivially bypassed via DevTools or a direct POST request; additionally, because the `wps_membership_plan` custom post type is registered with `capability_type => 'post'`, any user who can edit posts satisfies the `current_user_can('edit_post', $post_id)` guard in `save_meta_boxes()`. This makes it possible for authenticated attackers, with Contributor-level access and above, to escalate their privileges to Administrator by storing `'administrator'` as the role granted on membership acquisition, which the Pro companion plugin then applies via `add_role()` during membership lifecycle events. Successful exploitation requires the Subscriptions for WooCommerce Pro companion plugin to be active, as it is the component that reads the stored `_wps_plan_user_role` meta via `get_post_meta()` and calls `add_role()` to apply the role during membership lifecycle events.
Weakness: CWE-269
Which versions are affected by CVE-2026-15414?
How do I fix CVE-2026-15414?
No fix has been published for CVE-2026-15414 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-15414 being exploited?
There is no known exploitation of CVE-2026-15414 in the wild and no public exploit code.
Sources
Also known as GHSA-x6w6-m8vc-m6cp.