Skip to main content
WordPress plugin recordReviewed

WooCommerce Stripe gateway vulnerability records, and where its webhooks and connection are read

This gateway takes input at the checkout, in its settings and at a URL that Stripe calls.

How to read its records, including CVE-2023-34000, whose ranges and patched versions are split by release line, and where connection status, webhooks and express checkout buttons sit on a store you are authorised to review.

WooCommerce Stripe Payment Gateway vulnerability history

Source: Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . It lists 6 records for WooCommerce Stripe Payment Gateway. 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 11.1.0

Worked out from data retrieved on .

Every affected range listed in this source for WooCommerce Stripe Payment Gateway ends before version 11.1.0.

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 Stripe Payment Gateway 10.9.0 - 11.0.1 - Insecure Storage of Password

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.3)
    Affected versions
    • From version 10.9.0 up to and including 11.0.1

    Patched versions: 11.1.0

    Update to at least version 11.1.0.

  2. WooCommerce Stripe Payment Gateway <= 10.7.0 - Missing Authorization to Unauthenticated Order Status Manipulation via 'order' Parameter

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

    Patched versions: 10.8.0

    Update to at least version 10.8.0.

  3. WooCommerce Stripe Payment Gateway <= 7.6.1 - Insecure Direct Object Reference via update_payment_intent_ajax

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

    Patched versions: 7.6.2

    Update to at least version 7.6.2.

  4. Stripe Gateway <= 7.6.0 - Cross-Site Request Forgery

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.4)
    Affected versions
    • All versions before 7.6.1

    Patched versions: 7.6.1

    Update to at least version 7.6.1.

  5. WooCommerce Stripe Payment Gateway <= 7.4.0 - Missing Authorization

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

    Patched versions: 7.4.1

    Update to at least version 7.4.1.

Show 1 older record
  1. WooCommerce Stripe Payment Gateway <= 7.4.0 - Unauthenticated Insecure Direct Object Reference to Sensitive Information Disclosure

    Published:
    Last updated:
    Severity:
    High (CVSS 7.5)
    Affected versions
    21 affected ranges, one per release line: WooCommerce Stripe Payment Gateway <= 7.4.0 - Unauthenticated Insecure Direct Object Reference to Sensitive Information Disclosure
    • All versions up to and including 5.5.0
    • From version 5.5.0 up to, but not including, 5.5.1
    • From version 5.6.0 up to, but not including, 5.6.3
    • From version 5.7.0 up to, but not including, 5.7.1
    • From version 5.8.0 up to, but not including, 5.8.2
    • From version 5.9.0 up to, but not including, 5.9.1
    • From version 6.0.0 up to, but not including, 6.0.1
    • From version 6.1.0 up to, but not including, 6.1.1
    • From version 6.2.0 up to, but not including, 6.2.1
    • From version 6.3.0 up to, but not including, 6.3.1
    • From version 6.4.0 up to, but not including, 6.4.4
    • From version 6.5.0 up to, but not including, 6.5.2
    • From version 6.6.0 up to, but not including, 6.6.1
    • From version 6.7.0 up to, but not including, 6.7.1
    • From version 6.8.0 up to, but not including, 6.8.1
    • From version 6.9.0 up to, but not including, 6.9.1
    • From version 7.0.0 up to, but not including, 7.0.3
    • From version 7.1.0 up to, but not including, 7.1.1
    • From version 7.2.0 up to, but not including, 7.2.1
    • From version 7.3.0 up to, but not including, 7.3.1
    • Version 7.4.0 only

    Patched versions: 5.5.1, 5.6.3, 5.7.1, 5.8.2, 5.9.1, 6.0.1, 6.1.1, 6.2.1, 6.3.1, 6.4.4, 6.5.2, 6.6.1, 6.7.1, 6.8.1, 6.9.1, 7.0.3, 7.1.1, 7.2.1, 7.3.1, 7.4.1

    Update to at least the patched version for your release line: 5.5.1, 5.6.3, 5.7.1, 5.8.2, 5.9.1, 6.0.1, 6.1.1, 6.2.1, 6.3.1, 6.4.4, 6.5.2, 6.6.1, 6.7.1, 6.8.1, 6.9.1, 7.0.3, 7.1.1, 7.2.1, 7.3.1, 7.4.1.

Check WooCommerce Stripe Payment Gateway 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.

Checkout, webhooks and settings: where this gateway takes input

The WordPress.org listing for WooCommerce Stripe Payment Gateway calls it the official plugin created by Stripe and WooCommerce.

Read a WooCommerce Stripe gateway vulnerability record against the three places it takes input.

First, the checkout: the payment form; the express checkout buttons, which the vendor's express checkout guide lets a store show on pages including the checkout, product and cart pages; and, per its saved payment methods guide, My Account > Payment Methods, where customers can add, view and remove saved payment methods. That guide ties saving to the Enable saved payment methods setting.

Second, a URL that Stripe calls: the webhook guide says Stripe communicates to the extension via webhooks, and the order status guide says automatic order status updates only work if webhooks are configured correctly.

Third, the dashboard: the settings under WooCommerce > Settings > Payments > Stripe, and refunds, which the vendor says the extension can make from inside the WooCommerce interface. WooCommerce's roles page lists both, access to WooCommerce settings and processing refunds, among what a Shop Manager can do.

What the WooCommerce Stripe Payment Gateway vulnerabilities on record say

Four records from the history on this page are examples.

Of those four titles, two include the word Unauthenticated and two do not.

  • CVE-2026-2381 has a title ending Missing Authorization to Unauthenticated Order Status Manipulation via 'order' Parameter. Range: all versions up to and including 10.7.0. Patched: 10.8.0.
  • CVE-2023-51502 has a title ending Insecure Direct Object Reference via update_payment_intent_ajax. Range: all versions up to and including 7.6.1. Patched: 7.6.2.
  • CVE-2023-44999 is titled Stripe Gateway <= 7.6.0 - Cross-Site Request Forgery, a shorter name than the plugin's own. Range: all versions before 7.6.1. Patched: 7.6.1.
  • CVE-2023-34000 has a title ending Unauthenticated Insecure Direct Object Reference to Sensitive Information Disclosure. Its ranges and patched versions are split by release line.

CVE-2023-34000 and its release lines

Match the installed version on each record's affected range and patched versions field, not its title. CVE-2023-34000 has 7.4.0 in its title, yet its fields list all versions up to and including 5.5.0 and then give each release line from 5.5 to 7.4 its own range and patched version, such as 6.4.4 for the 6.4 line.

A store on 6.4.4 sits outside that record but inside the other three named here, whose ranges read all versions up to and including 10.7.0, all versions up to and including 7.6.1 and all versions before 7.6.1.

Before an update, read the vendor's documentation too: when read in November 2026, the first page of its Stripe extension documentation opened with a security update notice that named releases to install and linked to the vendor's own advisory. Where that notice and the update guidance at the top of the history differ, plan for the later release.

Where each Stripe gateway check lives

The vendor's settings guide enables a payment method by checking the box next to its name and clicking Save Changes.

These checks need neither: write down what each Stripe screen shows and leave without saving.

Plugin and WooCommerce versions, and update status

The installation guide says to look for WooCommerce Stripe Gateway under Plugins > Installed Plugins. WordPress shows each version in the Description column, and an update notice when a plugin hosted in its Plugin Directory has a newer version available.

Write down the Stripe and WooCommerce versions: the setup guide says PHP, WordPress and WooCommerce must be on recent versions. The vendor's November 2026 notice said to check the installed version there even if automatic updates are enabled.

Connection state

The connection guide says four statuses in the Account details section, Payment, Payout, Webhook and Sync, should all be green or Enabled. Write down each. For a Disabled Sync, the settings guide lists scenarios, the first being a connection that "uses manually entered API keys instead of OAuth." In the General section, note whether Enable test mode is ticked: the guide says it should likely be disabled unless you are testing payments, refunds, disputes or other such processes.

Clicking Configure connection, it says, shows the connection status, with Live and Test tabs. Record both and leave Disconnect alone.

Webhook configuration

In the Live and Test tabs, the webhook guide says the webhook status should read Configured. Write it down, with either dashboard notice the guide describes: the saved webhook endpoint no longer exists, or automatic reconfiguration was skipped. Do not press Reconfigure webhooks: the guide says reconfiguring creates a new webhook endpoint in the Stripe account and removes the endpoints the extension created before.

As a step of this page's own, ask the Stripe account owner to list each webhook endpoint in the Stripe dashboard and who added it.

The guide says the extension only uses the /?wc-api=wc_stripe format, and that any other endpoints seen in the Stripe dashboard likely come from other payment gateways or third-party services that integrate with Stripe.

Payment buttons

The vendor calls these express checkouts. Its guide names four, Amazon Pay, Apple Pay, Google Pay and Link by Stripe, enabled in the Express checkouts section under WooCommerce > Settings > Payments > Stripe > Payment Methods. Write down which are ticked. Per the guide, once the payment method settings are saved, links open each set's options.

There, it says, a preview of the buttons is followed by a list of the eligibility requirements, which ones are missing (if any) and where the buttons will appear. Copy that list.

Administration permissions

On the Users screen, the role filter links list accounts by role. Write down who holds Administrator and Shop Manager. Outside WordPress, the settings guide says many settings that pertain to the Stripe account, such as Radar rules, can only be changed in the Stripe dashboard. Ask the account owner who can sign in there.

Where a Stripe gateway version check stops

For WooCommerce Stripe Payment Gateway security, the version is a starting point: it places a store inside or outside each range on record.

It cannot tell you what reached the store while an affected release was installed, whether test mode is ticked on the live store, which endpoints sit in the Stripe account, or who holds Shop Manager.

A WordPress security audit adds a test of the checkout itself: on a staging copy or with the gateway in test mode, it changes prices, quantities and coupon codes in the cart and checkout requests, and checks that an order is marked paid only once the payment provider confirms it. Stripe's own hosted pages and platform are not tested.

Frequently asked questions

Compare the installed version with every record in the history. CVE-2026-2381 covers all versions up to and including 10.7.0, while CVE-2023-34000 lists all versions up to and including 5.5.0 and then a separate range and patched version for each release line from 5.5 to 7.4.

The WordPress.org listing is titled WooCommerce Stripe Payment Gateway. The vendor's installation guide says to look for WooCommerce Stripe Gateway, its documentation uses Stripe WooCommerce Extension and Stripe for WooCommerce, and the title of CVE-2023-44999 begins Stripe Gateway. Every record on this page is filed under one slug, woocommerce-gateway-stripe.

The vendor says card data is collected with Stripe Elements, which embeds a Stripe-hosted interface on the site via an iframe. For saved payment methods it says the exact details, such as the card number and CVC code, are not stored directly on the site. Its database guide says the extension stores various identifiers, for customers, cards and so on, in the site's database.

The checklist on this page suggests one. The webhook guide says the extension skips its automatic webhook changes when the saved webhook points to a different site's URL, such as on a staging copy. It also says reconfiguring creates a new webhook endpoint in the Stripe account and removes the endpoints the extension created before. On a copy, read the statuses and press nothing.

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.