Skip to main content
WordPress plugin recordReviewed

WooCommerce PayPal Payments vulnerability records, and what to read on a connected store

This plugin holds a store's PayPal connection, its webhooks and the buttons shoppers pay with.

Record titles in the source data use the words Unauthenticated, Order Manipulation and Information Disclosure. The checks here go past the version number.

WooCommerce PayPal Payments vulnerability history

Source: Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . It lists 3 records for WooCommerce PayPal Payments. 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 4.0.2

Worked out from data retrieved on .

Every affected range listed in this source for WooCommerce PayPal Payments ends before version 4.0.2.

A vendor can publish a security release before this source records it. Read the plugin's own changelog as well as this history.

  1. WooCommerce PayPal Payments <= 3.3.2 - Unauthenticated Sensitive Information Disclosure

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.3)
    Affected versions
    • All versions up to and including 3.3.2

    Patched versions: 3.4.0

    Update to at least version 3.4.0.

  2. WooCommerce PayPal Payments <= 4.0.1 - Missing Authorization to Unauthenticated Order Manipulation and Information Disclosure

    Published:
    Last updated:
    Severity:
    High (CVSS 8.2)
    Affected versions
    • All versions up to and including 4.0.1

    Patched versions: 4.0.2

    Update to at least version 4.0.2.

  3. WooCommerce PayPal Payments <= 2.0.4 - Cross-Site Request Forgery

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.3)
    Affected versions
    • All versions before 2.0.5

    Patched versions: 2.0.5

    Update to at least version 2.0.5.

Check WooCommerce PayPal Payments 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.

Where WooCommerce PayPal Payments takes input: shopper, PayPal and staff

A WooCommerce PayPal Payments vulnerability record is easier to read against the places the plugin takes input.

One is the shopper: the plugin's WordPress.org listing describes PayPal buttons displayed on product pages, in-cart and at checkout. Another is PayPal itself: the vendor's settings guide says webhooks allow the store to receive updates about transactions and events.

A third is the store's staff. The vendor's onboarding guide reaches the settings through WooCommerce > Settings > Payments > PayPal, and its orders guide has refunds issued from the order screen by clicking Refund via PayPal. WooCommerce's roles documentation says a Shop Manager can access WooCommerce settings and process refunds, and WordPress's own says an Administrator has access to all administration features within a single site.

What the WooCommerce PayPal Payments vulnerabilities on record say

Two of the records named here carry the word Unauthenticated in their titles, and both titles end in Information Disclosure.

The third title ends Cross-Site Request Forgery.

  • CVE-2026-9284, whose title ends Missing Authorization to Unauthenticated Order Manipulation and Information Disclosure. Affected: all versions up to and including 4.0.1. Patched: 4.0.2.
  • CVE-2025-14073, whose title ends Unauthenticated Sensitive Information Disclosure. Affected: all versions up to and including 3.3.2. Patched: 3.4.0.
  • CVE-2023-35917, whose title ends Cross-Site Request Forgery. Affected: all versions before 2.0.5. Patched: 2.0.5.

Publication order is not version order

The history on this page is ordered by publication date, which for this plugin is not version order. CVE-2025-14073 was published on 31 July 2026 with a range that stops at 3.3.2. CVE-2026-9284 was published earlier, on 22 May 2026, with a range that stops at 4.0.1. So compare the installed version with every range.

Match on the affected range and patched versions field, not the title: the title of CVE-2023-35917 carries 2.0.4, while its affected field reads all versions before 2.0.5.

Reading a live WooCommerce PayPal Payments setup

Where each check lives depends on the settings interface, so first write down which one the site shows.

The vendor keeps a legacy page for older versions that use the legacy settings interface, and its documentation hub says people who have used the plugin for a while may still see that interface. When read in November 2026, the hub also carried a note that its guide applies to PayPal Payments 4.x with the new settings interface, is still under development and may change. Read each screen and leave without saving.

Plugin and WooCommerce versions

On the Plugins screen, each row's Description column includes the version number. Write down the versions in the WooCommerce PayPal Payments row and the WooCommerce row. The listing's setup steps say the Payment methods list may include two PayPal options and to click PayPal, not PayPal Standard. Note which PayPal entries appear under WooCommerce > Settings > Payments.

Connection mode

For the new interface, the settings guide puts Connection Status on the Settings page: it displays the Merchant ID, Email Address and Client ID, and displays Sandbox when test credentials are in use. The legacy page describes a Connection tab that displays the REST API credentials, with a Sandbox checkbox that switches from live to sandbox accounts.

Write down live or sandbox, the Merchant ID and the email address, and keep any key shown there out of notes and screenshots.

Leave the Sandbox checkbox and Disconnect alone: the onboarding guide calls Disconnect's Start over option destructive and says it cannot be undone.

Webhook status

The legacy page says that for Alternative Payment Methods the buyer's payment is only captured after receiving a webhook confirmation, and the orders guide says refunds made on paypal.com are synced to the order through webhooks.

The settings guide lists Webhooks under Expert Settings and says you can see the events the store is subscribed to; the legacy page puts a Webhook Status section on the Connection tab.

Write down what is shown and the date. The settings guide gives Resubscribe and Simulate as steps for when order statuses stop updating. Both are actions, so leave them to the store's change process.

Button placement

In the settings guide's Styling section, the Location options include Cart, Classic Checkout, Express Checkout, Mini Cart and Product Page. The legacy page puts Smart Button Locations under Standard Payments. Write down every enabled location, Mini Cart in particular: the troubleshooting page says scripts load only where buttons or Pay Later messaging are enabled, and that the Mini Cart location appears on almost every page, so enabling it loads the scripts site-wide.

Administration permissions

On the Users screen, the role filter links show the users assigned to each role. List every Administrator and Shop Manager account and the person behind it. The vendor's orders guide issues a refund from the order by clicking Refund via PayPal, and WooCommerce's roles page says a Shop Manager can process refunds. Ask who in each role handles refunds.

WooCommerce PayPal Payments security past the version match

A version match tells you which records apply to that copy of the plugin.

What happened on the store in the meantime is a question for its logs. The troubleshooting page starts by turning Logging on, then opening WooCommerce > Status > Logs, and says logs are kept for 30 days. A store may therefore hold no log for the days that matter.

Nor does a version match show the setup: live or sandbox, where PayPal's scripts load, who holds Shop Manager, or whether the plugin's reCAPTCHA option is active. The vendor's fraud prevention page puts that option at WooCommerce > Settings > Integration > WooCommerce PayPal Payments reCAPTCHA and says the protection will only be active if both v2 and v3 keys were configured.

A WordPress security audit gives the checkout its own pass, on a staging copy or with the payment gateway in test mode, and lists every script that loads on the checkout page, so you know which third parties run code on the page where customers enter their details. PayPal's own hosted pages and platform stay outside the test.

Frequently asked questions

Each record has its own range, so check the installed version against each. CVE-2026-9284, for example, has an affected range of all versions up to and including 4.0.1 and lists 4.0.2 as patched. Then read the update guidance at the top of the history. The changelog on the plugin's WordPress.org listing gives each release under a dated version heading. Check it for later releases before you settle on a version to move to.

Read the installed version in the Description column of the Plugins screen and look for an update notice. The plugin's WordPress.org listing says automatic updates should work generally smoothly but still recommends a backup, and says to purge the website cache if the PayPal buttons do not appear after an update. Then compare the installed version with the update guidance at the top of the history and with the dated releases in the listing's changelog.

The plugin's WordPress.org listing says, in its setup steps, that the Payment methods list may include two PayPal options and to click PayPal, not PayPal Standard. The plugin's changelog has an entry about disabling the legacy PayPal Standard gateway when the merchant account is connected to PayPal Payments. This page's history is built only from entries filed under the slug woocommerce-paypal-payments, and being filed there does not tell you whether an entry also applies to PayPal Standard.

The vendor's saved payment methods page says Vaulting lets the plugin store a payment method as a token and that card data stays in PayPal's vault. Its card processing page describes the Advanced Card Processing fields as hosted fields on your website.

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 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 every record 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.