# CVE-2026-80311: Stripe Payment Forms by WP Full Pay < 8.5.5 - Cross-Customer Subscription Cancellation via IDOR

> An attacker with a valid session can cancel other customers' subscriptions by guessing high-entropy identifiers due to missing ownership verification.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **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:** 29 Aug 2026
- **Updated:** 30 Aug 2026
- **Also known as:** GHSA-prcx-3pc2-2j8x

## What is CVE-2026-80311?

CVE-2026-80311 is a medium-severity missing authorization vulnerability in Unknown Stripe Payment Forms by WP Full Pay, published on 29 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Stripe Payment Forms by WP Full Pay  WordPress plugin before 8.5.5 does not verify that a subscription belongs to the customer bound to the requesting customer-portal session before cancelling it, allowing a user with a confirmed portal session to cancel subscriptions belonging to other customers.

Exploitation requires the attacker to know the target subscription's identifier, which is high-entropy and not enumerable through the Stripe Payment Forms by WP Full Pay  WordPress plugin before 8.5.5.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-80311 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80311 is a medium-severity missing authorization vulnerability in Unknown Stripe Payment Forms by WP Full Pay, published on 29 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-80311 in the wild and no public exploit code.

Affected product: Unknown Stripe Payment Forms by WP Full Pay. 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-80311/ (Markdown: https://insights.sbomify.com/CVE-2026-80311/index.md)
```

## Sources

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

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