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.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
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
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.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
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: 1 proofs of concept on GitHub.
Sources
Also known as GHSA-26qv-fwp4-4p47.