CVE-2026-12432 json
Stripe Payment Forms by WP Full Pay <= 8.4.3 - Missing Authorization to Unauthenticated Payment Record Manipulation via 'paymentIntentId' Parameter
published 2026-06-27 4 mo ago modified 2026-06-29 4 mo ago also EUVD-2026-39957
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 46%
- public exploits
- 0
- none known
Summary
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.
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 4 mo ago
Exploit prediction
0.56% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
Affected products
- themeisle Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions
Classification
- Weakness
-
- CWE-862 Missing Authorization
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/c5811d13-0c5d-4a10-86a1-6318cc2e7663?source=cve
- plugins.trac.wordpress.org /browser/wp-full-stripe-free/tags/8.4.3/includes/wpfs-customer.php#L3865
- plugins.trac.wordpress.org /browser/wp-full-stripe-free/tags/8.4.3/includes/wpfs-customer.php#L706
- plugins.trac.wordpress.org /browser/wp-full-stripe-free/tags/8.4.3/includes/wpfs-customer.php#L3840
- plugins.trac.wordpress.org /browser/wp-full-stripe-free/tags/8.4.3/includes/wpfs-database.php#L2652
- plugins.trac.wordpress.org /browser/wp-full-stripe-free/tags/8.4.1/includes/wpfs-customer.php#L3865
- plugins.trac.wordpress.org /browser/wp-full-stripe-free/tags/8.4.1/includes/wpfs-customer.php#L706
- plugins.trac.wordpress.org /browser/wp-full-stripe-free/tags/8.4.1/includes/wpfs-customer.php#L3840
- plugins.trac.wordpress.org /browser/wp-full-stripe-free/tags/8.4.1/includes/wpfs-database.php#L2652
- plugins.trac.wordpress.org /changeset?sfp_email=&sfph_mail=&reponame=&old=3584355%40wp-full-stripe-free&new=3584355%40wp-full-stripe-free
Sources
- CVE List CVE-2026-12432
- NVD CVE-2026-12432
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.