Woocommerce Stripe Payment Gateway
Approved changes feed: RSS · Atom
cpe:2.3:a:woocommerce:woocommerce_stripe_payment_gateway:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Woocommerce (c7b0e075-8e70-51f0-86a8-e45639512f20) |
|---|---|
| Product | Woocommerce Stripe Payment Gateway (96d689be-07c3-5e5d-8d68-17571e87ed9b) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-2381 |
vulnerable | 2026-07-29 00:37:44.727890 |
WooCommerce Stripe Payment Gateway <= 10.7.0 - Missing Authorization to Unauthenticated Order Status Manipulation via 'order' Parameter
MEDIUM (6.5)
The WooCommerce Stripe Payment Gateway plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the `ajax_pay_for_order()` function in all versions up to, and including, 10.7.0 This is due to a missing order ownership or order_key verification when processing payment for an order via the `wc_stripe_pay_for_order` WC-AJAX endpoint. The function only validates a nonce (which is publicly available on any WooCommerce page where Express Checkout is enabled), but does not verify that the requesting user owns the target order and is allowed to modify it. This makes it possible for unauthenticated attackers to force any pending order into a failed status by providing a fake payment method, causing a payment exception that updates the order status to "failed" via sequential order ID enumeration.
Published: 2026-06-16T09:31:33.055Z
Updated: 2026-06-16T16:16:27.503Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-51502 |
vulnerable | 2026-06-08 06:17:53.354332 |
WordPress WooCommerce Stripe Payment Gateway Plugin <= 7.6.1 is vulnerable to Insecure Direct Object References (IDOR)
HIGH (7.5)
Authorization Bypass Through User-Controlled Key vulnerability in WooCommerce WooCommerce Stripe Payment Gateway.This issue affects WooCommerce Stripe Payment Gateway: from n/a through 7.6.1.
Published: 2024-01-05T07:56:31.944Z
Updated: 2026-04-28T16:09:03.166Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-44999 |
vulnerable | 2026-06-08 06:12:41.605949 |
WordPress WooCommerce Stripe Gateway plugin <= 7.6.0 - Cross Site Request Forgery (CSRF) vulnerability
MEDIUM (5.4)
Cross-Site Request Forgery (CSRF) vulnerability in WooCommerce WooCommerce Stripe Payment Gateway.This issue affects WooCommerce Stripe Payment Gateway: from n/a through 7.6.0.
Published: 2024-03-27T13:27:46.498Z
Updated: 2026-04-28T16:08:41.353Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-35049 |
vulnerable | 2026-06-08 06:06:26.447194 |
WordPress WooCommerce Stripe Payment Gateway plugin <= 7.4.0 - Unauthenticated Broken Access Control vulnerability
HIGH (7.5)
Missing Authorization vulnerability in WooCommerce WooCommerce Stripe Payment Gateway.This issue affects WooCommerce Stripe Payment Gateway: from n/a through 7.4.0.
Published: 2024-06-19T12:26:52.965Z
Updated: 2026-04-28T16:08:29.428Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-34000 |
vulnerable | 2026-06-08 06:06:24.177086 |
WordPress WooCommerce Stripe Payment Gateway Plugin <= 7.4.0 is vulnerable to Insecure Direct Object References (IDOR)
HIGH (7.5)
Unauth. IDOR vulnerability leading to PII Disclosure in WooCommerce Stripe Payment Gateway plugin <= 7.4.0 versions.
Published: 2023-06-14T07:30:11.268Z
Updated: 2026-04-28T16:08:26.449Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.