# CVE-2026-93511: Premium Packages < 7.2.1 - Unauthenticated PayPal Webhook Signature Verification Bypass

> Unauthenticated attackers can bypass PayPal webhook signature verification to forge payment confirmations and subscription cancellations in the Premium Packages plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-wv8r-wv6j-wh9g

## What is CVE-2026-93511?

CVE-2026-93511 is a medium-severity vulnerability in Unknown Premium Packages, published on 23 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Premium Packages  WordPress plugin before 7.2.1 does not verify PayPal's webhook signature before processing payment and subscription notifications, allowing unauthenticated attackers to forge payment confirmations and subscription-cancellation events against any order whose transaction id they know.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

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


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

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

## Is CVE-2026-93511 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93511 is a medium-severity vulnerability in Unknown Premium Packages, published on 23 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93511 in the wild and no public exploit code.

Affected product: Unknown Premium Packages. 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-93511/ (Markdown: https://insights.sbomify.com/CVE-2026-93511/index.md)
```

## Sources

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

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