Is CVE-2026-2381 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-2381 being exploited in the wild.

How severe is CVE-2026-2381?

Medium severity, with a CVSS score of 6.5, published 16 June 2026.

Which products and versions are affected?

WooCommerce Stripe Payment Gateway up to, and including, 10.7.0.

Is there a fix for CVE-2026-2381?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-2381 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-2381?

Check whether you run WooCommerce Stripe Payment Gateway at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-2381: WooCommerce Stripe Payment Gateway unauthorized order modification

CVE-2026-2381 · Severity: medium · CVSS 6.5 · Published 2026-06-16

The WooCommerce Stripe Payment Gateway plugin for WordPress, which allows businesses to accept credit card payments, contains a security flaw that allows unauthorized users to interfere with customer orders. An attacker can remotely force pending orders into a 'failed' status by submitting fake payment information. This can disrupt business operations, prevent successful sales, and negatively impact the customer experience by causing legitimate transactions to be cancelled.

Vendors: WooCommerce.

Quick answers

Is CVE-2026-2381 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-2381 being exploited in the wild.
How severe is CVE-2026-2381?: Medium severity, with a CVSS score of 6.5, published 16 June 2026.
Which products and versions are affected?: WooCommerce Stripe Payment Gateway up to, and including, 10.7.0.
Is there a fix for CVE-2026-2381?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-2381 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-2381?: Check whether you run WooCommerce Stripe Payment Gateway at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The WooCommerce Stripe Payment Gateway plugin is vulnerable to an authorization bypass due to a missing capability check on the `ajax_pay_for_order()` function within the `wc_stripe_pay_for_order` WC-AJAX endpoint. While the function validates a nonce, it fails to verify order ownership or the `order_key`. This allows unauthenticated attackers to use sequential order ID enumeration and provide fake payment methods to trigger payment exceptions. These exceptions force the target order's status to 'failed'. The vulnerability is patched in version 10.8.0.

Affected products

WooCommerce WooCommerce Stripe Payment Gateway up to, and including, 10.7.0

Timeline

2026-06-16: disclosed
2026-06-16: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.