WooCommerce Stripe Payment Gateway <= 10.7.0 - Missing Authorization to Unauthenticated Order Status Manipulation via 'order' Parameter
Strategic Overview
- Status
- Patched in 10.8.0
- Affected Plugin
- WooCommerce Stripe Payment Gateway
- Affected Version
<= 10.7.0- CVSS
- 6.5Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-2381
At a glance
CVE-2026-2381 is a medium-severity Missing Authorization vulnerability in the WooCommerce Stripe Payment Gateway WordPress plugin, affecting versions <= 10.7.0. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 10.8.0; sites on affected versions should update now. Disclosed June 2026, reported by Dmitrii Ignatyev.
Vulnerability Overview
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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
WooCommerce Stripe Payment Gateway <= 10.7.0 carries this weakness at failed, and reaching it takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For WooCommerce Stripe Payment Gateway the fix is 10.8.0: builds <= 10.7.0 are affected, anything from 10.8.0 onward is not.
Remediation
Update to version 10.8.0, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: WooCommerce Stripe Payment Gateway 10.8.0 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in WooCommerce Stripe Payment Gateway
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C