WooPayments: Integrated WooCommerce Payments at a glance
- 7 publicly disclosed vulnerabilities, 1 of them rated High or Critical. The most recent was disclosed on Mar 30, 2026.
- Ranked #76 by popularity on WordPress.org (800,000+ active installs).
- The latest version is 11.3.0 (released Nov 11, 2026). The most recent security fix shipped in 10.6.0.
- 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 WooPayments: Integrated WooCommerce Payments version
Enter the WooPayments: Integrated WooCommerce Payments 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 “WooPayments: Integrated WooCommerce Payments”, 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 “WooPayments: Integrated WooCommerce Payments”.
- 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 (11.3.0). 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 WooPayments: Integrated WooCommerce Payments vulnerabilities
WooPayments <= 10.5.1 - Missing Authorization to Unauthenticated Plugin Settings Update via save_upe_appearance_ajax
Missing authorization · CVE-2026-1710
Affected versions: ≤ 10.5.1
Fixed in: 10.6.0
Severity: Medium 6.5 · Disclosed Mar 30, 2026
WooPayments – Fully Integrated Solution Built and Supported by Woo <= 6.6.2 - Unauthenticated Insecure Direct Object Reference
Missing authorization · CVE-2023-51503
Affected versions: ≤ 6.6.2
Fixed in: 6.7.0
Severity: Medium 5.3 · Disclosed Dec 27, 2023
WooCommerce Payments <= 6.4.2 - Authenticated (Contributor+) Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2023-49828
Affected versions: ≤ 6.4.2
Fixed in: 6.5.0
Severity: Medium 6.4 · Disclosed Dec 5, 2023
WooCommerce Payments <= 5.9.0 - Authenticated (Shop manager+) SQL Injection via currency parameters
SQL injection · CVE-2023-35915
Affected versions: ≤ 5.9.0
Fixed in: 5.9.1
Severity: Medium 6.6 · Disclosed Jun 20, 2023
WooCommerce Payments <= 5.9.0 - Missing Authorization via redirect_pay_for_order_to_update_payment_method
Missing authorization · CVE-2023-35916
Affected versions: ≤ 5.9.0
Fixed in: 5.9.1
Severity: Medium 6.5 · Disclosed Jun 19, 2023
WooCommerce Payments 4.8.0 - 5.6.1 Authentication Bypass and Privilege Escalation
Privilege escalation · CVE-2023-28121
Affected versions: ≥ 4.8.0, ≤ 5.6.1
Fixed in: 5.6.2
Severity: Critical 9.8 · Disclosed Mar 23, 2023
WooCommerce Payments <= 4.5.0 - Payment Bypass
Other weakness
Affected versions: ≥ 4.3.0, < 4.3.1
Fixed in: 3.9.4, 4.0.3, 4.1.1, 4.2.2, 4.3.1, 4.4.1, 4.5.1
Severity: Medium 5.3 · Disclosed Aug 9, 2022
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| WooPayments <= 10.5.1 - Missing Authorization to Unauthenticated Plugin Settings Update via save_upe_appearance_ajaxMissing authorization · CVE-2026-1710 | ≤ 10.5.1 | 10.6.0 | Medium 6.5 | Mar 30, 2026 |
| WooPayments – Fully Integrated Solution Built and Supported by Woo <= 6.6.2 - Unauthenticated Insecure Direct Object ReferenceMissing authorization · CVE-2023-51503 | ≤ 6.6.2 | 6.7.0 | Medium 5.3 | Dec 27, 2023 |
| WooCommerce Payments <= 6.4.2 - Authenticated (Contributor+) Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2023-49828 | ≤ 6.4.2 | 6.5.0 | Medium 6.4 | Dec 5, 2023 |
| WooCommerce Payments <= 5.9.0 - Authenticated (Shop manager+) SQL Injection via currency parametersSQL injection · CVE-2023-35915 | ≤ 5.9.0 | 5.9.1 | Medium 6.6 | Jun 20, 2023 |
| WooCommerce Payments <= 5.9.0 - Missing Authorization via redirect_pay_for_order_to_update_payment_methodMissing authorization · CVE-2023-35916 | ≤ 5.9.0 | 5.9.1 | Medium 6.5 | Jun 19, 2023 |
| WooCommerce Payments 4.8.0 - 5.6.1 Authentication Bypass and Privilege EscalationPrivilege escalation · CVE-2023-28121 | ≥ 4.8.0, ≤ 5.6.1 | 5.6.2 | Critical 9.8 | Mar 23, 2023 |
| WooCommerce Payments <= 4.5.0 - Payment BypassOther weakness | ≥ 4.3.0, < 4.3.1 | 3.9.4, 4.0.3, 4.1.1, 4.2.2, 4.3.1, 4.4.1, 4.5.1 | Medium 5.3 | Aug 9, 2022 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Mar 30, 2026.
Most common weaknesses in WooPayments: Integrated WooCommerce Payments
Missing authorization
3 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.
SQL injection
1 issue
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 WooPayments: Integrated WooCommerce Payments safe to use?
WooPayments: Integrated WooCommerce Payments is a well-known plugin with 800,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 (11.3.0) and turn on automatic updates.
How do I find which version of WooPayments: Integrated WooCommerce Payments 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 vulnerabilitiesWooPayments: Integrated WooCommerce Payments on WordPress.org