# CVE-2026-74991: WPForms Lite 1.8.8.2 - 2.0.1.1 - Unauthenticated Stripe Refund and Subscription Cancellation via External PaymentIntent

> Unauthenticated attackers can trigger refunds and cancel subscriptions for other applications by submitting external Stripe payment objects.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/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:** 24 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-9x97-gpc7-wm62

## What is CVE-2026-74991?

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

### Official description

The WPForms  WordPress plugin before 2.0.2 does not verify that a Stripe payment object supplied during a public form submission belongs to it before acting on it, allowing unauthenticated users to trigger a full refund and an immediate subscription cancellation against payments created by other applications on the site owner's Stripe account.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-74991 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74991 is a medium-severity vulnerability in Unknown WPForms, published on 24 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-74991 in the wild and no public exploit code.

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

## Sources

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

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