WordPress security changelog
MEDIUM CVE-2026-12432 Deferred

Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions: A security weakness

Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is <= 8.4.3.

CVE / CNA score 5.3 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions
Plugin slug
wp-full-stripe-free
Affected
<= 8.4.3
Safe version
> 8.4.3
Published
Jun 27, 2026
Weakness
CWE-862 — Missing Authorization

This CVE was published Jun 27, 2026 and is one of 6 known issues for this plugin.

What to do

Update, patch or deactivate.

Update Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions to a release after 8.4.3, or disable and remove it until a fixed version is available.

A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

The WP Full Stripe Free plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 8.4.3 via the wpfs_update_failed_payment_status AJAX action. The handler is registered through both wp_ajax_ and wp_ajax_nopriv_ hooks and the underlying update_failed_payment_status() function performs no capability check, no nonce verification, and no logged-in check before calling $this->db->updatePaymentByEventId() with attacker-controlled POST parameters. This makes it possible for unauthenticated attackers who can obtain a valid Stripe Payment Intent ID for the target site (Payment Intent IDs are exposed to the customer browser during normal Stripe.js checkout flows) to manipulate payment records in the site's database, marking previously successful payments as failed and overwriting failure codes and messages with attacker-supplied values.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

References

Primary and upstream sources