Payment Gateway of Stripe for WooCommerce
payment-gateway-stripe-and-woocommerce-integration · plugin
Known security vulnerabilities for Payment Gateway of Stripe for WooCommerce. Find out in seconds which version runs on your site with WP Lens.
4 known vulnerabilities
1 critical · 4 exploitable without logging in · 1 with public exploit code · latest Sep 19, 2026
Before you install
Use with care
- 2 records needing no login published in the last two years.
If you install it, keep auto-updates on and monitor the site: when a new record appears you need to update quickly.
This assessment relies only on published vulnerability records and wordpress.org data; it does not review the code.
Is this component installed on your sites, and in which version? See it from inside the site with Noroxi Connector
Listed on wordpress.org · latest 5.1.1 · last updated Oct 9, 2026 · 7K+ installs
wordpress.org status checked on Nov 9, 2026
Vulnerabilities
- Critical 9.8
CVE-2023-3162unauthenticated≤ 3.7.7
Stripe Payment Plugin for WooCommerce <= 3.7.7 - Authentication Bypass
- High 7.5
CVE-2024-0705unauthenticated≤ 3.7.9
Stripe Payment Plugin for WooCommerce <= 3.7.9 - Unauthenticated SQL Injection
- Medium 6.5
CVE-2026-45217unauthenticated≤ 5.0.7
WordPress Stripe Payment Gateway for WooCommerce plugin <= 5.0.7 - Broken Authentication vulnerability
- Medium 5.3
CVE-2026-9832unauthenticated≤ 5.0.8
Payment Gateway of Stripe for WooCommerce <= 5.0.8 - Unauthenticated Improper Verification of Cryptographic Signature via woocommerce_api_wt_stripe Webhook Endp
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).
Exploited this week · every Monday
New KEV entries, fresh PoCs, WordPress triage and what to do this week. No account needed.