Auth bypass in Stripe Payment Forms By Wp Full Pay
CVE-2026-16734
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.
Vulnerability class: Broken Access Control
EPSS: 0.002 (9.6th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 7.5 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N.
Affected products
- Unknown Stripe Payment Forms By Wp Full Pay — versions 0
Weakness classification (CWE)
References
- contact@wpscan.com (technical-description, exploit, vdb-entry)
Frequently asked questions
- What is CVE-2026-16734?
- CVE-2026-16734 is a high-severity vulnerability in Stripe Payment Forms By Wp Full Pay, classified under Missing Authorization. CVSS score: 7.5/10. Published 2026-08-06.
- How severe is CVE-2026-16734?
- High severity. CVSS v3 base score is 7.5 out of 10.