← WordPress Vulnerabilities
WordPress security by component

Stripe For WooCommerce

Stripe For WooCommerce is a WordPress component with 2 published CVE records in this archive. The latest tracked vulnerability was published Jul 27, 2026; the highest CVE/CNA score is 7.5.

Plugin slug: woo-stripe-payment

CVE-2026-59530: Stripe For WooCommerce exposes an unauthenticated privileged operation

Stripe For WooCommerce through 4.0.7 permits an unauthenticated request to reach a plugin operation without the required access-control check. The Patchstack CNA record does not disclose the payment route, action, parameter, function, protected object or concrete operation, so the exact payment or order impact remains unknown.

PublishedJul 27, 2026
Known safe version4.0.8
Safe version
Jul 27, 2026 CVE-2026-59530
Stripe For WooCommerce exposes an unauthenticated privileged operation
Stripe For WooCommerce through 4.0.7 permits an unauthenticated request to reach a plugin operation without the required access-control check. The Patchstack CNA record does not disclose the payment route, action, parameter, function, protected object or concrete operation, so the exact payment or order impact remains unknown.
4.0.8
CVE7.5
NVDPending
Jul 24, 2026 CVE-2026-12654
Unsigned Stripe webhooks can mark arbitrary WooCommerce orders paid
Payment Plugins for Stripe WooCommerce through 4.0.7 accepts POST requests to /wp-json/wc-stripe/v1/webhook while the selected live or test webhook secret is blank, which is the plugin's default until a Stripe-issued secret is configured. An unauthenticated attacker can forge a charge.pending event whose metadata.order_id and metadata.gateway_id select a pending asynchronous order and payment gateway; a charge object with status=succeeded and captured=true reaches wc_stripe_process_charge_pending() and payment_complete(), marking the order paid and potentially starting fulfillment with an attacker-supplied transaction ID.
4.0.8
CVE5.3
NVDPending