Is Stripe Payment Forms by WP Full Pay safe to use?

Laskyr does not give safety verdicts. No known unpatched vulnerabilities in the latest version (8.5.8). As of 2026-11-04. 13 issues are on record for older versions; version 8.5.7 or newer fixes all of them that state a fix. Keep Stripe Payment Forms by WP Full Pay on the latest version (8.5.8) and remove it if you do not use it.

Which versions of Stripe Payment Forms by WP Full Pay are vulnerable?

Known issues on record (newest first): Missing authorization check (8.5.6 and older, fixed in 8.5.7); Missing authorization check (older than 8.5.5, fixed in 8.5.5); Information disclosure (older than 8.5.1, fixed in 8.5.1); Missing authorization check (older than 8.5.1, fixed in 8.5.1); Cross-site scripting (XSS) (8.5.0 and older, fixed in 8.5.1); Missing authorization check (older than 8.5.2, fixed in 8.5.2). The full list with sources is on this page.

What is the latest version of Stripe Payment Forms by WP Full Pay?

8.5.8, according to wordpress.org (last updated 2026-10-26). It has 8,000+ active installs.

What should I do if my Stripe Payment Forms by WP Full Pay is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update wp-full-stripe-free). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · wp-full-stripe-free · data as of 2026-11-04

Is Stripe Payment Forms by WP Full Pay safe? Known vulnerabilities and latest version

Latest version: 8.5.8
Last updated: 2026-10-26
Active installs: 8,000+
Known issues on record: 13
Unpatched in latest: 0
Tested up to WP: 7.1.4 · PHP 7.4+

🚀 Create Stripe payment forms for WordPress. Accept credit cards, Apple Pay, donations, subscriptions & more. Easy setup, no coding needed! — by Themeisle

What to do

Update to the latest version (8.5.8). Anything older than 8.5.7 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
If you cannot update right away, deactivate it until you can.
Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get wp-full-stripe-free --field=version shows what you run; wp plugin update wp-full-stripe-free updates it.

Check your version

Known vulnerabilities

13 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

high 7.5 CVE-2026-62073 · published 2026-10-01

Missing authorization check in Stripe Payment Forms by WP Full Pay (8.5.6 and older)

Affected: 8.5.6 and older
Fixed in: 8.5.7
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Unauthenticated Broken Access Control in WP Full Stripe Free <= 8.5.6 versions.

NVD CVE-2026-62073 Patchstack advisory

medium 4.3 CVE-2026-80311 · published 2026-08-29

Missing authorization check in Stripe Payment Forms by WP Full Pay (older than 8.5.5)

Affected: older than 8.5.5
Fixed in: 8.5.5
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by CISA ADP

Details from the advisory

The Stripe Payment Forms by WP Full Pay WordPress plugin before 8.5.5 does not verify that a subscription belongs to the customer bound to the requesting customer-portal session before cancelling it, allowing a user with a confirmed portal session to cancel subscriptions belonging to other customers. Exploitation requires the attacker to know the target subscription's identifier, which is high-entropy and not enumerable through the Stripe Payment Forms by WP Full Pay WordPress plugin before 8.5.5.

NVD CVE-2026-80311 WPScan advisory

medium 5.3 CVE-2026-77758 · published 2026-08-26

Information disclosure in Stripe Payment Forms by WP Full Pay (older than 8.5.1)

Affected: older than 8.5.1
Fixed in: 8.5.1
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by CISA ADP

Details from the advisory

The Stripe Payment Forms by WP Full Pay WordPress plugin before 8.5.1 does not properly verify that a customer portal session has completed its confirmation step before returning data, allowing unauthenticated users to read another customer's subscription and billing information.

NVD CVE-2026-77758 WPScan advisory

medium 4.3 CVE-2026-77789 · published 2026-08-26

Missing authorization check in Stripe Payment Forms by WP Full Pay (older than 8.5.1)

Affected: older than 8.5.1
Fixed in: 8.5.1
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by CISA ADP

Details from the advisory

The Stripe Payment Forms by WP Full Pay WordPress plugin before 8.5.1 does not verify that a subscription belongs to the customer bound to the requesting customer-portal session before acting on it, allowing a user with a confirmed portal session to cancel, reactivate or modify subscriptions belonging to other customers.

NVD CVE-2026-77789 WPScan advisory

high 7.1 CVE-2026-61960 · published 2026-08-13

Cross-site scripting (XSS) in Stripe Payment Forms by WP Full Pay (8.5.0 and older)

Affected: 8.5.0 and older
Fixed in: 8.5.1
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Unauthenticated Cross Site Scripting (XSS) in WP Full Stripe Free <= 8.5.0 versions.

NVD CVE-2026-61960 Patchstack advisory

high 7.5 CVE-2026-16734 · published 2026-08-06

Missing authorization check in Stripe Payment Forms by WP Full Pay (older than 8.5.2)

Affected: older than 8.5.2
Fixed in: 8.5.2
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by CISA ADP

Details from the advisory

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.

NVD CVE-2026-16734 WPScan advisory

medium 5.3 CVE-2026-12432 · published 2026-06-27

Missing authorization check in Stripe Payment Forms by WP Full Pay (8.4.3 and older)

Affected: 8.4.3 and older
Fixed in: 8.5.0 *
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

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.

NVD CVE-2026-12432 Wordfence advisory Code change (fix)Plugin source

medium 6.5 CVE-2026-42378 · published 2026-06-15

Authentication bypass in Stripe Payment Forms by WP Full Pay (8.4.1 and older)

Affected: 8.4.1 and older
Fixed in: 8.4.2
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Subscriber Broken Authentication in WP Full Stripe Free <= 8.4.1 versions.

NVD CVE-2026-42378 Patchstack advisory

high 7.5 CVE-2025-9322 · published 2025-10-25

SQL injection in Stripe Payment Forms by WP Full Pay (8.3.1 and older)

Affected: 8.3.1 and older
Fixed in: 8.3.2 *
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

The Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions plugin for WordPress is vulnerable to SQL Injection via the 'wpfs-form-name' parameter in all versions up to, and including, 8.3.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

NVD CVE-2025-9322 Wordfence advisory Code change (fix)

high 7.6 CVE-2025-58789 · published 2025-09-05

SQL injection in Stripe Payment Forms by WP Full Pay (8.2.5 and older)

Affected: 8.2.5 and older
Fixed in: 8.2.6
Access needed (per CVSS): Needs an admin-level account
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Themeisle WP Full Stripe Free wp-full-stripe-free allows SQL Injection.This issue affects WP Full Stripe Free: from n/a through <= 8.2.5.

NVD CVE-2025-58789 Patchstack advisory

high 8.8 CVE-2023-47667 · published 2023-11-18

Cross-site request forgery (CSRF) in Stripe Payment Forms by WP Full Pay (7.0.16 and older)

Affected: 7.0.16 and older
Fixed in: 7.0.18
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

Cross-Site Request Forgery (CSRF) vulnerability in Mammothology WP Full Stripe Free.This issue affects WP Full Stripe Free: from n/a through 7.0.16.

NVD CVE-2023-47667 Patchstack advisory

medium 4.8 CVE-2023-46088 · published 2023-10-26

Stored cross-site scripting (XSS) in Stripe Payment Forms by WP Full Pay (1.6.1 and older)

Affected: 1.6.1 and older
Fixed in: 7.0.5 *
Access needed (per CVSS): Needs an admin-level account; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

Auth. (admin+) Stored Cross-Site Scripting (XSS) vulnerability in Mammothology WP Full Stripe Free plugin <= 1.6.1 versions.

NVD CVE-2023-46088 Patchstack advisory

medium 4.8 CVE-2023-28934 · published 2023-08-08

Stored cross-site scripting (XSS) in Stripe Payment Forms by WP Full Pay (1.6.1 and older)

Affected: 1.6.1 and older
Fixed in: 7.0.5 *
Access needed (per CVSS): Needs an admin-level account; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

Auth. (admin+) Stored Cross-Site Scripting (XSS) vulnerability in Mammothology WP Full Stripe Free plugin <= 1.6.1 versions.

NVD CVE-2023-28934 Patchstack advisory

Recent activity

2026-10-26 — latest release on wordpress.org (8.5.8).
2026-10-01 — Missing authorization check disclosed (CVE-2026-62073), fixed in 8.5.7.
2026-08-29 — Missing authorization check disclosed (CVE-2026-80311), fixed in 8.5.5.
2026-08-26 — Information disclosure disclosed (CVE-2026-77758), fixed in 8.5.1.

Free. We check the CVE feeds every day and email you only when a new issue for Stripe Payment Forms by WP Full Pay (wp-full-stripe-free) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Missing authorization (5) · Cross-site scripting (XSS) (3) · SQL injection (2) · Sensitive data exposure (1) · Authentication bypass (1) · Cross-site request forgery (CSRF) (1)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/wp-full-stripe-free (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/wp-full-stripe-free"><img src="https://laskyr.com/plugins/wp-full-stripe-free/badge.svg" alt="Stripe Payment Forms by WP Full Pay vulnerability status"></a>

← Check another plugin · Free hacked-site scan

Is Stripe Payment Forms by WP Full Pay safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (8.5.8)

What to do

Check your version

Known vulnerabilities

Missing authorization check in Stripe Payment Forms by WP Full Pay (8.5.6 and older)

Missing authorization check in Stripe Payment Forms by WP Full Pay (older than 8.5.5)

Information disclosure in Stripe Payment Forms by WP Full Pay (older than 8.5.1)

Missing authorization check in Stripe Payment Forms by WP Full Pay (older than 8.5.1)

Cross-site scripting (XSS) in Stripe Payment Forms by WP Full Pay (8.5.0 and older)

Missing authorization check in Stripe Payment Forms by WP Full Pay (older than 8.5.2)

Missing authorization check in Stripe Payment Forms by WP Full Pay (8.4.3 and older)

Authentication bypass in Stripe Payment Forms by WP Full Pay (8.4.1 and older)

SQL injection in Stripe Payment Forms by WP Full Pay (8.3.1 and older)

SQL injection in Stripe Payment Forms by WP Full Pay (8.2.5 and older)

Cross-site request forgery (CSRF) in Stripe Payment Forms by WP Full Pay (7.0.16 and older)

Stored cross-site scripting (XSS) in Stripe Payment Forms by WP Full Pay (1.6.1 and older)

Stored cross-site scripting (XSS) in Stripe Payment Forms by WP Full Pay (1.6.1 and older)

Recent activity

Get an email when Stripe Payment Forms by WP Full Pay has a new vulnerability

Browse vulnerabilities

Where this data comes from