Payment Plugins for Stripe WooCommerce at a glance
- 4 publicly disclosed vulnerabilities. The most recent was disclosed on Oct 9, 2026.
- Ranked #392 by popularity on WordPress.org (100,000+ active installs).
- The latest version is 4.0.21 (released Nov 19, 2026). The most recent security fix shipped in 4.0.18.
- 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 Payment Plugins for Stripe WooCommerce version
Enter the Payment Plugins for Stripe WooCommerce 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 “Payment Plugins for Stripe WooCommerce”, 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 “Payment Plugins for Stripe WooCommerce”.
- 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 (4.0.21). 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 Payment Plugins for Stripe WooCommerce vulnerabilities
Payment Plugins for Stripe WooCommerce <= 4.0.17 - Reflected DOM-Based Cross-Site Scripting via '#response' URL Fragment
Cross-site scripting (XSS) · CVE-2026-89100
Affected versions: ≤ 4.0.17
Fixed in: 4.0.18
Severity: Medium 6.1 · Disclosed Oct 9, 2026
Payment Plugins for Stripe WooCommerce <= 4.0.11 - Unauthenticated Information Exposure
Information disclosure · CVE-2026-80339
Affected versions: ≤ 4.0.11
Fixed in: 4.0.12
Severity: Medium 5.3 · Disclosed Sep 7, 2026
Payment Plugins for Stripe WooCommerce <= 4.0.7 - Missing Authorization to Unauthenticated Arbitrary Order Status Modification via Empty Webhook Secret
Missing authorization · CVE-2026-12654
Affected versions: ≤ 4.0.7
Fixed in: 4.0.8
Severity: Medium 5.3 · Disclosed Jul 23, 2026
Payment Plugins for Stripe WooCommerce <= 4.0.7 - Missing Authorization
Missing authorization · CVE-2026-59530
Affected versions: ≤ 4.0.7
Fixed in: 4.0.8
Severity: Medium 5.3 · Disclosed Jul 23, 2026
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| Payment Plugins for Stripe WooCommerce <= 4.0.17 - Reflected DOM-Based Cross-Site Scripting via '#response' URL FragmentCross-site scripting (XSS) · CVE-2026-89100 | ≤ 4.0.17 | 4.0.18 | Medium 6.1 | Oct 9, 2026 |
| Payment Plugins for Stripe WooCommerce <= 4.0.11 - Unauthenticated Information ExposureInformation disclosure · CVE-2026-80339 | ≤ 4.0.11 | 4.0.12 | Medium 5.3 | Sep 7, 2026 |
| Payment Plugins for Stripe WooCommerce <= 4.0.7 - Missing Authorization to Unauthenticated Arbitrary Order Status Modification via Empty Webhook SecretMissing authorization · CVE-2026-12654 | ≤ 4.0.7 | 4.0.8 | Medium 5.3 | Jul 23, 2026 |
| Payment Plugins for Stripe WooCommerce <= 4.0.7 - Missing AuthorizationMissing authorization · CVE-2026-59530 | ≤ 4.0.7 | 4.0.8 | Medium 5.3 | Jul 23, 2026 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Oct 9, 2026.
Most common weaknesses in Payment Plugins for Stripe WooCommerce
Missing authorization
2 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)
1 issue
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.
Information disclosure
1 issue
Data that should stay private, such as user details or configuration values, can be read from outside.
Frequently asked questions
Is Payment Plugins for Stripe WooCommerce safe to use?
Payment Plugins for Stripe WooCommerce is a well-known plugin with 100,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 (4.0.21) and turn on automatic updates.
How do I find which version of Payment Plugins for Stripe WooCommerce 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 vulnerabilitiesPayment Plugins for Stripe WooCommerce on WordPress.org