CVE-2026-12654 MEDIUM

CVE-2026-12654: Payment Plugins for Stripe WooCommerce <= 4.0.7 - Missing Authorization to Unauthenticated Arbitrary Order Status Modification via Empty Webhook Secret

Vendor Paymentplugins
Product Payment Plugins for Stripe WooCommerce
Weakness CWE-862 · Missing authorization
Published July 24, 2026
Last update July 24, 2026

CVSS base score

5.3/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction None
Confidentiality None
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

What the vulnerability does

01Description

The Payment Plugins for Stripe WooCommerce plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 4.0.7. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to mark arbitrary pending asynchronous WooCommerce orders as paid by forging a charge.pending event with attacker-controlled metadata.order_id, metadata.gateway_id, and a charge object carrying status=succeeded and captured=true, triggering payment_complete() and downstream fulfillment flows with an attacker-supplied transaction ID. Exploitation requires the merchant to have left the webhook_secret_test or webhook_secret_live option blank, which is the plugin's default state until a Stripe-issued whsec_ value is manually configured; once a non-empty secret is set, the signature verification cannot be bypassed.

Explanation of Vulnerability in Simple Terms

02Summary

The Payment Plugins for Stripe WooCommerce plugin through version 4.0.7 lacks proper authorization checks, allowing unauthenticated attackers to modify payment-related data. An attacker can send network requests without authentication to alter sensitive information. Site owners should update immediately to prevent unauthorized changes to payment settings or transaction records.

What an attacker can do

03Attacker Capabilities

Modify payment settings or transaction data without logging in.

Potential impact on your site

04Site Impact

Attackers can alter payment configurations, potentially disrupting transactions or redirecting funds.

Conditions required to exploit

05Prerequisites

Network access only; no authentication or user interaction required.

Key dates

06Disclosure timeline

July 24, 2026 CVE published

Related vulnerabilities

08Related CVE