CVE-2026-12432: CWE-862 Missing Authorization in themeisle Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions
The WP Full Stripe Free plugin for WordPress (Stripe Payment Forms by WP Full Pay) contains a missing authorization vulnerability in versions up to and including 8.4.3. The vulnerability exists in the wpfs_update_failed_payment_status AJAX action, which lacks capability checks, nonce verification, and logged-in user verification. This allows unauthenticated attackers who have a valid Stripe Payment Intent ID to manipulate payment records, marking successful payments as failed and overwriting failure details.
AI Analysis
Technical Summary
CVE-2026-12432 describes a missing authorization vulnerability (CWE-862) in the WP Full Stripe Free plugin for WordPress, specifically in the wpfs_update_failed_payment_status AJAX handler. This handler is accessible via both authenticated and unauthenticated AJAX hooks (wp_ajax_ and wp_ajax_nopriv_) and does not perform any capability checks, nonce verification, or logged-in user validation before updating payment records in the database. An attacker with a valid Stripe Payment Intent ID, which is exposed to customers during normal Stripe.js checkout flows, can exploit this to alter payment statuses and failure messages arbitrarily.
Potential Impact
An unauthenticated attacker can manipulate payment records by marking previously successful payments as failed and injecting arbitrary failure codes and messages. This impacts the integrity of payment data but does not disclose sensitive information or cause denial of service. The vulnerability has a CVSS 3.1 base score of 5.3 (medium severity), reflecting network attack vector, low complexity, no privileges required, no user interaction, no confidentiality or availability impact, and limited integrity impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict access to the AJAX endpoint if possible or implement custom authorization checks. Monitor for updates from the vendor themeisle regarding a security patch or official fix.
CVE-2026-12432: CWE-862 Missing Authorization in themeisle Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions
Description
The WP Full Stripe Free plugin for WordPress (Stripe Payment Forms by WP Full Pay) contains a missing authorization vulnerability in versions up to and including 8.4.3. The vulnerability exists in the wpfs_update_failed_payment_status AJAX action, which lacks capability checks, nonce verification, and logged-in user verification. This allows unauthenticated attackers who have a valid Stripe Payment Intent ID to manipulate payment records, marking successful payments as failed and overwriting failure details.
CVSS v3.1
Score 5.3medium
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-12432 describes a missing authorization vulnerability (CWE-862) in the WP Full Stripe Free plugin for WordPress, specifically in the wpfs_update_failed_payment_status AJAX handler. This handler is accessible via both authenticated and unauthenticated AJAX hooks (wp_ajax_ and wp_ajax_nopriv_) and does not perform any capability checks, nonce verification, or logged-in user validation before updating payment records in the database. An attacker with a valid Stripe Payment Intent ID, which is exposed to customers during normal Stripe.js checkout flows, can exploit this to alter payment statuses and failure messages arbitrarily.
Potential Impact
An unauthenticated attacker can manipulate payment records by marking previously successful payments as failed and injecting arbitrary failure codes and messages. This impacts the integrity of payment data but does not disclose sensitive information or cause denial of service. The vulnerability has a CVSS 3.1 base score of 5.3 (medium severity), reflecting network attack vector, low complexity, no privileges required, no user interaction, no confidentiality or availability impact, and limited integrity impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict access to the AJAX endpoint if possible or implement custom authorization checks. Monitor for updates from the vendor themeisle regarding a security patch or official fix.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-06-16T18:12:09.808Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a3f79f727e9c79719e9f859
Added to database: 06/27/2026, 07:21:27 UTC
Last enriched: 06/27/2026, 07:36:55 UTC
Last updated: 06/27/2026, 07:44:48 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.