# CVE-2026-15397: Missing authorization in Subscriptions for WooCommerce

> Authenticated shop managers can install arbitrary plugins due to missing authorization checks in the AJAX handler.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jul 2026
- **Updated:** 30 Jul 2026
- **Also known as:** GHSA-36gg-fcqh-hw2c

## What is CVE-2026-15397?

CVE-2026-15397 is a high-severity missing authorization vulnerability in wpswings Subscriptions for WooCommerce, published on 30 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Subscriptions for WooCommerce plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 2.0.0. This is due to the plugin not properly verifying that a user is authorized to perform an action via the wps_sfw_install_plugin_configuration AJAX handler. This makes it possible for authenticated attackers, with shop manager-level access and above, to install and activate arbitrary WordPress.org plugins.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-15397?


## How do I fix CVE-2026-15397?

No fix has been published for CVE-2026-15397 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-15397 being exploited?

There is no known exploitation of CVE-2026-15397 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15397 is a high-severity missing authorization vulnerability in wpswings Subscriptions for WooCommerce, published on 30 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-15397 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-15397/ (Markdown: https://insights.sbomify.com/CVE-2026-15397/index.md)
```

## Sources

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

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