PatchSiren cyber security CVE debrief
CVE-2026-2381 woocommerce CVE debrief
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.
- Vendor
- woocommerce
- Product
- WooCommerce Stripe Payment Gateway
- CVSS
- MEDIUM 6.5
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-06-16
- Original CVE updated
- 2026-06-16
- Advisory published
- 2026-06-16
- Advisory updated
- 2026-06-16
Who should care
Users of the WooCommerce Stripe Payment Gateway plugin for WordPress, particularly those with versions up to and including 10.7.0, should be aware of this vulnerability and take steps to mitigate it.
Technical summary
The vulnerability exists in the `ajax_pay_for_order()` function of the WooCommerce Stripe Payment Gateway plugin. The function lacks a capability check, allowing unauthenticated attackers to modify order status.
Defensive priority
High
Recommended defensive actions
- Update the WooCommerce Stripe Payment Gateway plugin to a version beyond 10.7.0.
- Implement additional security measures to verify order ownership and user capabilities for payment processing.
Evidence notes
The vulnerability was reported by [email protected] and is documented in various sources including CVE.org and NVD.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-2381 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-2381
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-2381 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-2381
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://plugins.trac.wordpress.org/browser/woocommerce-gateway-stripe/tags/10.3.1/includes/class-wc-gateway-stripe.php
-
Source reference
Unverified legacy reference
URL: https://plugins.trac.wordpress.org/browser/woocommerce-gateway-stripe/tags/10.3.1/includes/payment-methods/class-wc-stripe-express-checkout-ajax-handler.php
-
Source reference
Unverified legacy reference
URL: https://plugins.trac.wordpress.org/changeset/3564842/woocommerce-gateway-stripe/trunk/includes/payment-methods/class-wc-stripe-express-checkout-ajax-handler.php
-
Source reference
Unverified legacy reference
URL: https://research.cleantalk.org/cve-2026-2381
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.