# 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.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Aug 2026
- **Updated:** 3 Aug 2026
- **Also known as:** GHSA-x6w6-m8vc-m6cp

## 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 (Improper Privilege Management)

## 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.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-15414 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-15414 in the wild and no public exploit code.

Affected product: wpswings Subscriptions for WooCommerce. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-15414/ (Markdown: https://insights.sbomify.com/CVE-2026-15414/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-15414
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-15414
- OSV: https://osv.dev/vulnerability/CVE-2026-15414

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-15414/
Summaries are generated and may contain mistakes; the official description above is the record.