Skip to content
Laskyr

Plugins · payment-gateway-stripe-and-woocommerce-integration · data as of 2026-11-04

Is Payment Gateway of Stripe for WooCommerce safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (5.1.1)

As of 2026-11-04. 4 issues are on record for older versions; version 5.0.9 or newer fixes all of them that state a fix.

Latest version
5.1.1
Last updated
2026-10-09
Active installs
7,000+
Known issues on record
4
Unpatched in latest
0
Tested up to WP
7.1.4 · PHP 5.6+

Integrate Stripe Payment Gateway in WooCommerce and accept cards, Google Pay, Apple Pay, Klarna, Alipay, and more with seamless, secure checkout. — by ThemeHigh

What to do

  1. Update to the latest version (5.1.1). Anything older than 5.0.9 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
  2. If you cannot update right away, deactivate it until you can.
  3. Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
  4. If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get payment-gateway-stripe-and-woocommerce-integration --field=version shows what you run; wp plugin update payment-gateway-stripe-and-woocommerce-integration updates it.

Check your version

Known vulnerabilities

4 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

medium 5.3 CVE-2026-9832 · published 2026-09-19

Security issue in Payment Gateway of Stripe for WooCommerce (5.0.8 and older)

Affected
5.0.8 and older
Fixed in
5.0.9 *
Access needed (per CVSS)
No login needed
Range from
CVE record (the advisory publisher) · score by Wordfence
Details from the advisory

The Payment Gateway of Stripe for WooCommerce plugin for WordPress is vulnerable to Improper Verification of Cryptographic Signature in all versions up to, and including, 5.0.8. This is due to the publicly accessible `woocommerce_api_wt_stripe` webhook endpoint (`EH_Stripe_Webhook_Handler::handle()`) wrapping the only call to `\Stripe\Webhook::constructEvent()` inside an `if (!empty($endpoint_secret))` guard that is never entered on default installations — because the `eh_stripe_webhook_secret` option is empty after a fresh plugin install — causing the raw, attacker-controlled POST body to be decoded and processed as a fully trusted Stripe event without any signature verification, authentication, or authorization. This makes it possible for unauthenticated attackers to send forged Stripe webhook events to manipulate WooCommerce order statuses, including marking unpaid orders as paid or completed via `payment_complete()`, forcing legitimate orders into a failed state, fabricating dispute notifications, and injecting forged refund events. This vulnerability is only exploitable when the Stripe webhook signing secret has not been configured by an administrator; once a valid signing secret is saved, `\Stripe\Webhook::constructEvent()` is enforced and forged requests are rejected.

NVD CVE-2026-9832Wordfence advisoryCode change (fix)Plugin source

medium 6.5 CVE-2026-45217 · published 2026-05-25

Authentication bypass in Payment Gateway of Stripe for WooCommerce (5.0.7 and older)

Affected
5.0.7 and older
Fixed in
5.0.8
Access needed (per CVSS)
No login needed
Range from
CVE record (the advisory publisher) · score by Patchstack
Details from the advisory

Authentication Bypass Using an Alternate Path or Channel vulnerability in ThemeHigh Stripe Payment Gateway for WooCommerce allows Password Recovery Exploitation. This issue affects Stripe Payment Gateway for WooCommerce: from n/a through 5.0.7.

NVD CVE-2026-45217Patchstack advisory

high 7.5 CVE-2024-0705 · published 2024-01-19

SQL injection in Payment Gateway of Stripe for WooCommerce (3.7.9 and older)

Affected
3.7.9 and older
Fixed in
3.8.0 *
Access needed (per CVSS)
No login needed
Range from
CVE record (the advisory publisher) · score by NVD
Details from the advisory

The Stripe Payment Plugin for WooCommerce plugin for WordPress is vulnerable to SQL Injection via the 'id' parameter in all versions up to, and including, 3.7.9 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

NVD CVE-2024-0705Wordfence advisoryCode change (fix)

critical 9.8 CVE-2023-3162 · published 2023-08-31

Authentication bypass in Payment Gateway of Stripe for WooCommerce (3.7.7 and older)

Affected
3.7.7 and older
Fixed in
3.7.8 *
Access needed (per CVSS)
No login needed
Range from
CVE record (the advisory publisher) · score by Wordfence
Details from the advisory

The Stripe Payment Plugin for WooCommerce plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 3.7.7. This is due to insufficient verification on the user being supplied during a Stripe checkout through the plugin. This allows unauthenticated attackers to log in as users who have orders, who are typically customers.

NVD CVE-2023-3162Wordfence advisoryCode change (fix)Plugin source

Recent activity

Browse vulnerabilities

Where this data comes from

Badge for your site or docs (states facts with a date, not a verdict):
Payment Gateway of Stripe for WooCommerce vulnerability status badge
<a href="https://laskyr.com/plugins/payment-gateway-stripe-and-woocommerce-integration"><img src="https://laskyr.com/plugins/payment-gateway-stripe-and-woocommerce-integration/badge.svg" alt="Payment Gateway of Stripe for WooCommerce vulnerability status"></a>

← Check another plugin · Free hacked-site scan

First hour checklist

If the site was just hacked, read the emergency kit before you delete files. The page is free. Email is optional.

Read the emergency kit