# CVE-2026-12432: Missing authorization in Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions

> Unauthenticated attackers can manipulate payment records by exploiting missing authorization checks in the WP Full Pay 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:** 27 Jun 2026
- **Updated:** 29 Jun 2026
- **Also known as:** GHSA-26qv-fwp4-4p47

## What is CVE-2026-12432?

CVE-2026-12432 is a medium-severity missing authorization vulnerability in themeisle Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions, published on 27 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WP Full Stripe Free plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 8.4.3 via the wpfs_update_failed_payment_status AJAX action. The handler is registered through both wp_ajax_ and wp_ajax_nopriv_ hooks and the underlying update_failed_payment_status() function performs no capability check, no nonce verification, and no logged-in check before calling $this->db->updatePaymentByEventId() with attacker-controlled POST parameters. This makes it possible for unauthenticated attackers who can obtain a valid Stripe Payment Intent ID for the target site (Payment Intent IDs are exposed to the customer browser during normal Stripe.js checkout flows) to manipulate payment records in the site's database, marking previously successful payments as failed and overwriting failure codes and messages with attacker-supplied values.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-12432 being exploited?

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

Public exploit code:

- WP Full Stripe Free <= 8.4.3 - Missing Authorization (github_poc): https://github.com/Polosss/By-Poloss..-..CVE-2026-12432-PoC

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12432 is a medium-severity missing authorization vulnerability in themeisle Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions, published on 27 Jun 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-12432 in the wild and no public exploit code.

Affected product: themeisle Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions. 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-12432/ (Markdown: https://insights.sbomify.com/CVE-2026-12432/index.md)
```

## Sources

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

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