CVE-2026-16734: CWE-862 Missing Authorization in Stripe Payment Forms by WP Full Pay
The Stripe Payment Forms by WP Full Pay WordPress plugin before 8.5.2 does not verify that the caller owns the Stripe payment intent referenced by two unauthenticated payment-form AJAX actions, allowing an unauthenticated visitor — using a nonce that is embedded in every public page containing a payment form — to change the amount of a payment intent that the Stripe Payment Forms by WP Full Pay WordPress plugin before 8.5.2 then updates server-side through the Stripe API with the store's secret key. An ownership check added in 8.5.0 was applied to only one payment-intent handler, leaving the pricing-recalculation and payment-intent-update actions unprotected against amount manipulation.
AI Analysis
Technical Summary
CVE-2026-16734 is a missing authorization vulnerability (CWE-862) in the Stripe Payment Forms by WP Full Pay WordPress plugin versions prior to 8.5.2. The plugin fails to verify that the caller owns the Stripe payment intent referenced in two unauthenticated payment-form AJAX actions. An unauthenticated attacker can exploit this by using a nonce embedded in public pages to change the amount of a payment intent. Although version 8.5.0 introduced an ownership check, it was only applied to one payment-intent handler, leaving the pricing-recalculation and payment-intent-update actions vulnerable to manipulation. The plugin then updates the payment intent server-side through the Stripe API using the store's secret key, potentially allowing unauthorized payment amount changes.
Potential Impact
An unauthenticated attacker can manipulate the amount of a payment intent processed by the Stripe Payment Forms plugin, potentially causing incorrect payment amounts to be charged or processed. This could lead to financial loss or fraud for the store using the plugin. The vulnerability affects the integrity of payment processing by allowing unauthorized modification of payment details.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Users should upgrade to version 8.5.2 or later once available, as the description indicates fixes were made in that version. Until then, restrict access to payment form AJAX actions or disable the plugin if possible to prevent exploitation.
CVE-2026-16734: CWE-862 Missing Authorization in Stripe Payment Forms by WP Full Pay
Description
The Stripe Payment Forms by WP Full Pay WordPress plugin before 8.5.2 does not verify that the caller owns the Stripe payment intent referenced by two unauthenticated payment-form AJAX actions, allowing an unauthenticated visitor — using a nonce that is embedded in every public page containing a payment form — to change the amount of a payment intent that the Stripe Payment Forms by WP Full Pay WordPress plugin before 8.5.2 then updates server-side through the Stripe API with the store's secret key. An ownership check added in 8.5.0 was applied to only one payment-intent handler, leaving the pricing-recalculation and payment-intent-update actions unprotected against amount manipulation.
CVSS v3.1
Score 7.5high
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-16734 is a missing authorization vulnerability (CWE-862) in the Stripe Payment Forms by WP Full Pay WordPress plugin versions prior to 8.5.2. The plugin fails to verify that the caller owns the Stripe payment intent referenced in two unauthenticated payment-form AJAX actions. An unauthenticated attacker can exploit this by using a nonce embedded in public pages to change the amount of a payment intent. Although version 8.5.0 introduced an ownership check, it was only applied to one payment-intent handler, leaving the pricing-recalculation and payment-intent-update actions vulnerable to manipulation. The plugin then updates the payment intent server-side through the Stripe API using the store's secret key, potentially allowing unauthorized payment amount changes.
Potential Impact
An unauthenticated attacker can manipulate the amount of a payment intent processed by the Stripe Payment Forms plugin, potentially causing incorrect payment amounts to be charged or processed. This could lead to financial loss or fraud for the store using the plugin. The vulnerability affects the integrity of payment processing by allowing unauthorized modification of payment details.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Users should upgrade to version 8.5.2 or later once available, as the description indicates fixes were made in that version. Until then, restrict access to payment form AJAX actions or disable the plugin if possible to prevent exploitation.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- WPScan
- Date Reserved
- 2026-07-23T07:37:13.516Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a742933bf8831d53945d742
Added to database: 08/06/2026, 06:26:59 UTC
Last enriched: 08/06/2026, 06:47:00 UTC
Last updated: 08/07/2026, 02:07:29 UTC
Views: 13
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.
External Links
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.