# CVE-2026-2001: WowRevenue <= 2.1.3 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Plugin Installation/Activation

> Authenticated subscribers can install arbitrary plugins due to missing capability checks, potentially leading to remote code execution on WordPress sites.

- **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:** 16 Feb 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-8qf9-59wm-rx63

## What is CVE-2026-2001?

CVE-2026-2001 is a high-severity missing authorization vulnerability in wpxpo WowRevenue – Product Bundles & Bulk Discounts, published on 16 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The WowRevenue plugin for WordPress is vulnerable to unauthorized plugin installation due to a missing capability check in the 'Notice::install_activate_plugin' function in all versions up to, and including, 2.1.3. This makes it possible for authenticated attackers, with subscriber-level access and above, to install arbitrary plugins on the affected site's server which may make remote code execution possible.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-2001 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-2001 is a high-severity missing authorization vulnerability in wpxpo WowRevenue – Product Bundles & Bulk Discounts, published on 16 Feb 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-2001 in the wild and no public exploit code.

Affected product: wpxpo WowRevenue – Product Bundles & Bulk Discounts. 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-2001/ (Markdown: https://insights.sbomify.com/CVE-2026-2001/index.md)
```

## Sources

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

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