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 version 8.5.2 contains a missing authorization vulnerability. This flaw allows unauthenticated users to manipulate the amount of a Stripe payment intent via two AJAX actions that do not verify ownership. Although an ownership check was introduced in version 8.5.0, it was only applied to one handler, leaving other payment-intent update actions unprotected. This vulnerability can lead to unauthorized modification of payment amounts without authentication.
AI Analysis
Technical Summary
CVE-2026-16734 describes 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 AJAX actions related to payment forms. An attacker can exploit this by using a nonce embedded in public pages to change the payment amount server-side via the Stripe API using the store's secret key. Although version 8.5.0 introduced an ownership check, it was only applied to one payment-intent handler, leaving other handlers vulnerable until fixed in 8.5.2.
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 impacts the integrity of payment transactions but does not disclose sensitive data or cause denial of service. The vulnerability allows unauthorized modification of payment intent amounts via the Stripe API using the store's secret key.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vulnerability is fixed in version 8.5.2 by applying proper ownership checks to all relevant payment-intent handlers. Until patched, restrict access to payment form AJAX actions or disable the plugin 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 version 8.5.2 contains a missing authorization vulnerability. This flaw allows unauthenticated users to manipulate the amount of a Stripe payment intent via two AJAX actions that do not verify ownership. Although an ownership check was introduced in version 8.5.0, it was only applied to one handler, leaving other payment-intent update actions unprotected. This vulnerability can lead to unauthorized modification of payment amounts without authentication.
CVSS v3.1
Score 7.5high
Affected software
Stripe Payment Forms by WP Full Pay
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-16734 describes 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 AJAX actions related to payment forms. An attacker can exploit this by using a nonce embedded in public pages to change the payment amount server-side via the Stripe API using the store's secret key. Although version 8.5.0 introduced an ownership check, it was only applied to one payment-intent handler, leaving other handlers vulnerable until fixed in 8.5.2.
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 impacts the integrity of payment transactions but does not disclose sensitive data or cause denial of service. The vulnerability allows unauthorized modification of payment intent amounts via the Stripe API using the store's secret key.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vulnerability is fixed in version 8.5.2 by applying proper ownership checks to all relevant payment-intent handlers. Until patched, restrict access to payment form AJAX actions or disable the plugin to prevent exploitation.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- WPScan
- Date Reserved
- 2026-07-23T07:37:13.516Z
- State
- PUBLISHED
Threat ID: 6a742933bf8831d53945d742
Added to database: 08/06/2026, 06:26:59 UTC
Last enriched: 08/13/2026, 17:28:05 UTC
Last updated: 09/21/2026, 22:01:32 UTC
Views: 61
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.