Is CVE-2026-12654 exploited in the wild?

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

How severe is CVE-2026-12654?

Medium severity, with a CVSS score of 5.3, published 24 July 2026.

Which products and versions are affected?

Payment Plugins for Stripe WooCommerce up to, and including, 4.0.7.

Is there a fix for CVE-2026-12654?

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-12654 attacked?

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

Am I affected by CVE-2026-12654?

Check whether you run Payment Plugins for Stripe WooCommerce 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-12654: Payment Plugins Stripe WooCommerce authorization bypass in webhooks

CVE-2026-12654 · Severity: medium · CVSS 5.3 · Published 2026-07-24

A vulnerability in a popular WordPress payment plugin for Stripe allows unauthorized individuals to mark pending orders as paid without actually providing payment. This could lead to financial loss for merchants as the system may automatically trigger the shipment of goods or provide access to digital services for fraudulent transactions. The issue occurs when the merchant has not yet configured a specific security secret provided by Stripe.

Vendors: Payment Plugins.

Quick answers

Is CVE-2026-12654 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-12654 being exploited in the wild.
How severe is CVE-2026-12654?: Medium severity, with a CVSS score of 5.3, published 24 July 2026.
Which products and versions are affected?: Payment Plugins for Stripe WooCommerce up to, and including, 4.0.7.
Is there a fix for CVE-2026-12654?: 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-12654 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-12654?: Check whether you run Payment Plugins for Stripe WooCommerce 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 Payment Plugins for Stripe WooCommerce plugin for WordPress (versions <= 4.0.7) contains a missing authorization vulnerability (CWE-862) in its webhook handling logic. Unauthenticated attackers can forge a 'charge.pending' event with malicious metadata (order_id and gateway_id) and a status of 'succeeded'. This triggers the payment_complete() function and downstream fulfillment flows. The vulnerability is exploitable if the merchant has left the 'webhook_secret_test' or 'webhook_secret_live' options blank, which is the default state. Once a non-empty secret is configured, signature verification prevents the bypass.

Affected products

Payment Plugins Payment Plugins for Stripe WooCommerce up to, and including, 4.0.7

Timeline

2026-07-24: disclosed: CVE published to NVD dataset

References

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