CVE-2026-16734

Stripe Payment Forms by WP Full Pay < 8.5.2 - Unauthenticated Payment Intent Amount Manipulation

Published Aug 6, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability allows an unauthenticated visitor to modify the amount field of a Stripe payment intent through two AJAX actions in the WP Full Pay plugin. The plugin fails to verify ownership of the payment intent, relying only on a nonce that is embedded on public pages. By altering the amount and sending the request to the server, the plugin uses the store’s secret key to update the intent directly via Stripe’s API, resulting in fraudulent charges or incorrect billing. This represents a weakness due to missing role‑based access control (CWE-862).

Affected Systems

Any WordPress site that uses the Stripe Payment Forms by WP Full Pay plugin version earlier than 8.5.2 is affected. The issue exists across all installations of that plugin where the pre‑8.5.2 version is deployed, regardless of site configuration.

Risk and Exploitability

Risk and exploitability: The vulnerability yields a CVSS score of 7.5, indicating high severity. The flaw permits financial manipulation without authentication. An attacker can send a crafted request to an AJAX endpoint that includes a nonce embedded in public pages, override the payment‑intent amount, and trigger the plugin to use the store's secret key to update the intent in Stripe. The EPSS score indicates a probability of exploitation of less than 1%, and the vulnerability is not listed in the CISA KEV catalog. Nonetheless, the potential for revenue loss and customer trust damage warrants urgent attention.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the WP Full Pay plugin to version 8.5.2 or later, which includes an ownership check for all payment‑intent handlers.
  • Disable or remove any custom AJAX endpoints that expose payment‑intent manipulation to unauthenticated users, if upgrade is not immediately possible.
  • Regularly monitor Stripe logs and webhook events for unauthorized payment‑intent updates, and investigate any anomalies.

Generated by OpenCVE AI on August 13, 2026 at 10:13 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-284
Type Values Removed Values Added
Weaknesses CWE-284
Type Values Removed Values Added
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.
Title Stripe Payment Forms by WP Full Pay < 8.5.2 - Unauthenticated Payment Intent Amount Manipulation
References

Subscriptions

No data.

Weaknesses

Sources

Status
PUBLISHED
Assigner
WPScan
Published
Updated
Aug 6, 2026, 2:33 PM
Reserved
Jul 23, 2026, 7:37 AM
Status
Deferred
Published
Aug 6, 2026, 7:16 AM
Modified
Aug 26, 2026, 4:31 PM