WooPayments vulnerability records, under the plugin's current and earlier names
What the source data records for WooPayments and for WooCommerce Payments, its earlier name, and where to read the connection, Safe Mode, checkout settings and account owners on a store you are authorised to review.
On this page
WooPayments vulnerability history
Source: Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . It lists 7 records for WooPayments. Copyright notices, licence terms and a link to each source record are under Data source and licence at the foot of this page.
Update to at least version 10.6.0
Worked out from data retrieved on .
Every affected range listed in this source for WooPayments ends before version 10.6.0.
A vendor can publish a security release before this source records it. Read the plugin's own changelog as well as this history.
WooPayments <= 10.5.1 - Missing Authorization to Unauthenticated Plugin Settings Update via save_upe_appearance_ajax
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.5)
- CVE:
- CVE-2026-1710
Affected versions- All versions up to and including 10.5.1
Patched versions: 10.6.0
Update to at least version 10.6.0.
WooPayments - Fully Integrated Solution Built and Supported by Woo <= 6.6.2 - Unauthenticated Insecure Direct Object Reference
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.3)
- CVE:
- CVE-2023-51503
Affected versions- All versions up to and including 6.6.2
Patched versions: 6.7.0
Update to at least version 6.7.0.
WooCommerce Payments <= 6.4.2 - Authenticated (Contributor+) Stored Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.4)
- CVE:
- CVE-2023-49828
Affected versions- All versions up to and including 6.4.2
Patched versions: 6.5.0
Update to at least version 6.5.0.
WooCommerce Payments <= 5.9.0 - Authenticated (Shop manager+) SQL Injection via currency parameters
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.6)
- CVE:
- CVE-2023-35915
Affected versions- All versions up to and including 5.9.0
Patched versions: 5.9.1
Update to at least version 5.9.1.
WooCommerce Payments <= 5.9.0 - Missing Authorization via redirect_pay_for_order_to_update_payment_method
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.5)
- CVE:
- CVE-2023-35916
Affected versions- All versions up to and including 5.9.0
Patched versions: 5.9.1
Update to at least version 5.9.1.
Show 2 older recordsHide the older records
WooCommerce Payments 4.8.0 - 5.6.1 Authentication Bypass and Privilege Escalation
- Published:
- Last updated:
- Severity:
- Critical (CVSS 9.8)
- CVE:
- CVE-2023-28121
Affected versions- From version 4.8.0 up to and including 5.6.1
Patched versions: 5.6.2
Update to at least version 5.6.2.
WooCommerce Payments <= 4.5.0 - Payment Bypass
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.3)
Affected versions7 affected ranges, one per release line: WooCommerce Payments <= 4.5.0 - Payment BypassHide the ranges: WooCommerce Payments <= 4.5.0 - Payment Bypass
- From version 3.9.0 up to, but not including, 3.9.4
- From version 4.0.0 up to, but not including, 4.0.3
- From version 4.1.0 up to, but not including, 4.1.1
- From version 4.2.0 up to, but not including, 4.2.2
- From version 4.3.0 up to, but not including, 4.3.1
- From version 4.4.0 up to, but not including, 4.4.1
- Version 4.5.0 only
Patched versions: 3.9.4, 4.0.3, 4.1.1, 4.2.2, 4.3.1, 4.4.1, 4.5.1
Update to at least the patched version for your release line: 3.9.4, 4.0.3, 4.1.1, 4.2.2, 4.3.1, 4.4.1, 4.5.1.
Check WooPayments on a live site
Read-only checks for a site you own or are authorised to review. Each step uses the WordPress dashboard or WP-CLI and sends no test payloads to the site.
What WooPayments is, and the three places it takes input
WooPayments is a payment plugin published by WooCommerce.
Its WordPress.org listing says it accepts major credit and debit cards on a WooCommerce store, with transactions viewed and managed from the WordPress dashboard, and calls it "previously WooCommerce Payments".
Three parts of a store belong to it: the checkout, where the vendor's documentation says hosted payment fields collect the card details; the Payments menu in the dashboard; and a connection to WordPress.com, which the listing says the plugin cannot be used without.
Titles in the history include the words Unauthenticated, Authenticated (Contributor+) and Authenticated (Shop manager+).
Where each WooPayments check is read, and what not to press
The Plugins screen shows each version in the Description column. Write down the WooPayments and WooCommerce rows. The vendor's Startup Guide suggests enabling automatic updates for both plugins there. Where the Automatic update column is shown, note what it shows for each without clicking its link, which enables or disables auto-updates for that plugin.
The vendor's connection page says WooPayments needs a connection to WordPress.com to work, and that the Jetpack Connection card under Settings > Connectors shows its state. A changelog entry in the plugin's readme says an update "lets the connection owner hand it to another administrator from Settings > Connectors on WordPress 7.0 or later." WooCommerce > Status is a second place to read the connection, and the one to use where a site shows no Connectors screen.
It has a WooPayments section, where the vendor's account page finds the Account ID and the plugin's own help text describes rows including Connected to WPCOM, Test Mode and Dev Mode. Write down each value.
If a Safe Mode notice is showing, record it and press neither of its two buttons. The vendor's Safe Mode page says Transfer your connection moves all WooPayments data to the new URL and disconnects the site at the original URL.
WooCommerce's own webhooks, which its documentation describes as notifications the store sends to a URL of your choice, are managed at WooCommerce > Settings > Advanced > Webhooks. Write down each one's name, and its Status where the list shows it.
WooPayments' changelog, which the plugin's readme keeps at greater length than its listing, mentions webhooks too, in entries such as "Avoid a fatal when a dispute webhook references an unknown charge." The vendor pages cited here describe no screen for those.
The Safe Mode page lists dispute and refund updates among features that may not be available, or will at least be unreliable, while Safe Mode is active. Carry the Safe Mode result into this item.
The vendor's Settings Guide puts these under Payments > Settings and notes that changes do not take effect until they are saved with the Save Changes button. Read the screen and leave without saving. The settings to write down include Enable WooPayments, Test mode, the methods enabled under Payments accepted on checkout and Express checkouts, Enable payments via saved cards, Enable manual capture and the Fraud protection risk level.
On the Users screen, the role filter links list the accounts in each role. Write down every Administrator and Shop Manager, a role WooCommerce documents as able to process refunds, among other things. Then ask about three owners that WordPress roles do not show.
First, the WordPress.com connection: the vendor's connection page says a new connection owner must already be an administrator on the site, with their own WordPress.com account. Second, the Account notifications address, which the Settings Guide says is treated as an owner-level contact for support purposes: anyone with access to it can request account changes or retrieve account information through the support team.
Third, the Stripe Express account: the vendor's access page says the Edit details link on Payments > Overview takes you to connect.stripe.com to log in, with a 6-digit code sent to your phone number or, through Verify with email, emailed to you. Ask whose phone and email those are, and leave the link alone.
What the version cannot say about WooPayments security
Comparing the installed WooPayments version with each range answers one question: whether that copy sits inside a range on record.
It is silent on whether the store was attacked while that version ran, on who owns the WordPress.com connection, on where Account notifications are sent, and on whether a cloned copy is sitting in Safe Mode.
A WordPress security audit starts logged out, calling without a session each REST route and admin-ajax action that plugins register for logged-out visitors. It also captures the requests an administrator makes in plugin settings screens, which for WooPayments sit under Payments > Settings, and replays them as a subscriber.
Frequently asked questions
It depends on the record, and a WooPayments range can start partway: CVE-2023-28121 runs from version 4.8.0 up to and including 5.6.1, so an install older than 4.8.0 sits outside it but inside CVE-2023-35915, whose range is all versions up to and including 5.9.0. Compare the installed version with every range in the history. Then read the update guidance at the top of the history and the vendor's Startup Guide: when read in November 2026, that guide opened with an advisory dated 3 November 2026 that says a security update is available for WooPayments. Where the two disagree, work towards the later release.
On the Plugins screen, read the version in the Description column; WordPress displays an update notice there when a plugin hosted in its directory has a newer version. Compare it with the update guidance at the top of the history and with the plugin's changelog, shown on its WordPress.org listing and kept at greater length in its readme, which words some entries as security work, such as "Security update." Where the changelog marks a later release that way, plan for that release.
The vendor's documentation says card details like the number and CVC are never stored on your site, and that a saved card is referenced by a payment token stored by its payment partner. It says WooCommerce stores non-payment details such as the customer's name, address and country in the site's WordPress database.
The vendor's Safe Mode page lists cloning a site from production to staging among the address changes that activate Safe Mode. Its test accounts page warns against turning development mode off on a staging or development copy: if the live account is connected to the copy, the copy could start taking real payments. On a copy, record the Safe Mode notice and the Dev Mode line under WooCommerce > Status, and change neither.
Scope the right test for your application
Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.
Data source and licenceHide the data source and licence
The vulnerability records on this page come from Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . The records contain material that is subject to copyright. Each copyright notice and its licence are reproduced once below, followed by a link to every source record.
Copyright 2012-2026 Defiant Inc.
Applies to every record listed below.
Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.
Copyright 1999-2026 The MITRE Corporation
Applies to 6 of the 7 records listed below.
CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.
Source records
- WooPayments <= 10.5.1 - Missing Authorization to Unauthenticated Plugin Settings Update via save_upe_appearance_ajax (CVE-2026-1710)
- WooPayments - Fully Integrated Solution Built and Supported by Woo <= 6.6.2 - Unauthenticated Insecure Direct Object Reference (CVE-2023-51503)
- WooCommerce Payments <= 6.4.2 - Authenticated (Contributor+) Stored Cross-Site Scripting (CVE-2023-49828)
- WooCommerce Payments <= 5.9.0 - Authenticated (Shop manager+) SQL Injection via currency parameters (CVE-2023-35915)
- WooCommerce Payments <= 5.9.0 - Missing Authorization via redirect_pay_for_order_to_update_payment_method (CVE-2023-35916)
- WooCommerce Payments 4.8.0 - 5.6.1 Authentication Bypass and Privilege Escalation (CVE-2023-28121)
- WooCommerce Payments <= 4.5.0 - Payment Bypass