Stripe Payment Forms by WP Full Pay at a glance
- 12 publicly disclosed vulnerabilities, 2 of them rated High or Critical. The most recent was disclosed on Oct 1, 2026.
- Ranked #2410 by popularity on WordPress.org (8,000+ active installs).
- The latest version is 8.5.8 (released Oct 26, 2026). The most recent security fix shipped in 8.5.7.
- Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
- The first thing to do: update to the latest version and turn on automatic updates.
Check your Stripe Payment Forms by WP Full Pay version
Enter the Stripe Payment Forms by WP Full Pay version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.
Your version number is compared on this page only. It is not sent anywhere.
Get an email when a new vulnerability is disclosed
We'll tell you when a new vulnerability is disclosed in “Stripe Payment Forms by WP Full Pay”, with the version that fixes it. Free, email address only, stop any time.
We use your email address only for these alerts. Privacy policy
Want every plugin and theme on your site checked daily?
With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.
How to check whether your site is affected
- 1
Find your version
In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Stripe Payment Forms by WP Full Pay”.
- 2
Compare it with the list below
If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.
- 3
Update
Click “Update now” to move to the latest version (8.5.8). Taking a backup first is a good idea.
- 4
Turn on automatic updates
On the same screen, click “Enable auto-updates” so future fixes are installed automatically.
Known Stripe Payment Forms by WP Full Pay vulnerabilities
Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions <= 8.5.6 - Missing Authorization
Missing authorization · CVE-2026-62073
Affected versions: ≤ 8.5.6
Fixed in: 8.5.7
Severity: Medium 5.3 · Disclosed Oct 1, 2026
Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions < 8.5.5 - Unauthenticated Insecure Direct Object Reference
Missing authorization · CVE-2026-80311
Affected versions: < 8.5.5
Fixed in: 8.5.5
Severity: Medium 5.3 · Disclosed Aug 27, 2026
Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions < 8.5.1 - Unauthenticated Information Exposure
Information disclosure · CVE-2026-77758
Affected versions: < 8.5.1
Fixed in: 8.5.1
Severity: Medium 5.3 · Disclosed Aug 24, 2026
Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions < 8.5.1 - Unauthenticated Insecure Direct Object Reference
Missing authorization · CVE-2026-77789
Affected versions: < 8.5.1
Fixed in: 8.5.1
Severity: Medium 5.3 · Disclosed Aug 24, 2026
Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions <= 8.5.0 - Unauthenticated Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2026-61960
Affected versions: ≤ 8.5.0
Fixed in: 8.5.1
Severity: High 7.2 · Disclosed Aug 6, 2026
Stripe Payment Forms by WP Full Pay <= 8.5.1 - Missing Authorization
Missing authorization · CVE-2026-16734
Affected versions: ≤ 8.5.1
Fixed in: 8.5.2
Severity: Medium 5.3 · Disclosed Jul 30, 2026
Stripe Payment Forms by WP Full Pay <= 8.4.3 - Missing Authorization to Unauthenticated Payment Record Manipulation via 'paymentIntentId' Parameter
Missing authorization · CVE-2026-12432
Affected versions: ≤ 8.4.3
Fixed in: 8.5.0
Severity: Medium 5.3 · Disclosed Jun 26, 2026
Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions <= 8.4.1 - Missing Authorization
Missing authorization · CVE-2026-42378
Affected versions: ≤ 8.4.1
Fixed in: 8.4.2
Severity: Medium 4.3 · Disclosed Jun 1, 2026
Stripe Payment Forms <= 8.3.1 - Unauthenticated SQL Injection
SQL injection · CVE-2025-9322
Affected versions: ≤ 8.3.1
Fixed in: 8.3.2
Severity: High 7.5 · Disclosed Oct 24, 2025
WP Full Stripe Free <= 8.2.5 - Authenticated (Administrator+) SQL Injection
SQL injection · CVE-2025-58789
Affected versions: ≤ 8.2.5
Fixed in: 8.2.6
Severity: Medium 4.9 · Disclosed Sep 5, 2025
WP Full Stripe Free <= 7.0.17 - Cross-Site Request Forgery
Cross-site request forgery (CSRF) · CVE-2023-47667
Affected versions: ≤ 7.0.17
Fixed in: 7.0.18
Severity: Medium 4.3 · Disclosed Nov 8, 2023
WP Full Stripe Free <= 7.0.5 - Authenticated (Administrator+) Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2023-28934
Affected versions: ≤ 7.0.5
Fixed in: 7.0.6
Severity: Medium 4.4 · Disclosed Jul 5, 2023
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions <= 8.5.6 - Missing AuthorizationMissing authorization · CVE-2026-62073 | ≤ 8.5.6 | 8.5.7 | Medium 5.3 | Oct 1, 2026 |
| Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions < 8.5.5 - Unauthenticated Insecure Direct Object ReferenceMissing authorization · CVE-2026-80311 | < 8.5.5 | 8.5.5 | Medium 5.3 | Aug 27, 2026 |
| Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions < 8.5.1 - Unauthenticated Information ExposureInformation disclosure · CVE-2026-77758 | < 8.5.1 | 8.5.1 | Medium 5.3 | Aug 24, 2026 |
| Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions < 8.5.1 - Unauthenticated Insecure Direct Object ReferenceMissing authorization · CVE-2026-77789 | < 8.5.1 | 8.5.1 | Medium 5.3 | Aug 24, 2026 |
| Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions <= 8.5.0 - Unauthenticated Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2026-61960 | ≤ 8.5.0 | 8.5.1 | High 7.2 | Aug 6, 2026 |
| Stripe Payment Forms by WP Full Pay <= 8.5.1 - Missing AuthorizationMissing authorization · CVE-2026-16734 | ≤ 8.5.1 | 8.5.2 | Medium 5.3 | Jul 30, 2026 |
| Stripe Payment Forms by WP Full Pay <= 8.4.3 - Missing Authorization to Unauthenticated Payment Record Manipulation via 'paymentIntentId' ParameterMissing authorization · CVE-2026-12432 | ≤ 8.4.3 | 8.5.0 | Medium 5.3 | Jun 26, 2026 |
| Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions <= 8.4.1 - Missing AuthorizationMissing authorization · CVE-2026-42378 | ≤ 8.4.1 | 8.4.2 | Medium 4.3 | Jun 1, 2026 |
| Stripe Payment Forms <= 8.3.1 - Unauthenticated SQL InjectionSQL injection · CVE-2025-9322 | ≤ 8.3.1 | 8.3.2 | High 7.5 | Oct 24, 2025 |
| WP Full Stripe Free <= 8.2.5 - Authenticated (Administrator+) SQL InjectionSQL injection · CVE-2025-58789 | ≤ 8.2.5 | 8.2.6 | Medium 4.9 | Sep 5, 2025 |
| WP Full Stripe Free <= 7.0.17 - Cross-Site Request ForgeryCross-site request forgery (CSRF) · CVE-2023-47667 | ≤ 7.0.17 | 7.0.18 | Medium 4.3 | Nov 8, 2023 |
| WP Full Stripe Free <= 7.0.5 - Authenticated (Administrator+) Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2023-28934 | ≤ 7.0.5 | 7.0.6 | Medium 4.4 | Jul 5, 2023 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Oct 1, 2026.
Most common weaknesses in Stripe Payment Forms by WP Full Pay
Missing authorization
6 issues
Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.
Cross-site scripting (XSS)
2 issues
An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.
SQL injection
2 issues
Input such as a form field can be used to rewrite the queries the site sends to its database. Attackers use it to pull out customer, member or order data.
Frequently asked questions
Is Stripe Payment Forms by WP Full Pay safe to use?
Stripe Payment Forms by WP Full Pay is a well-known plugin with 8,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (8.5.8) and turn on automatic updates.
How do I find which version of Stripe Payment Forms by WP Full Pay my site is running?
In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.
Could updating break my site?
Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.
Can I check all my other plugins too?
Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.
Check every plugin and theme automatically, every day
Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.
Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.
← All plugin vulnerabilitiesStripe Payment Forms by WP Full Pay on WordPress.org