CVE-2026-12654Network attack vector

Unauthenticated order fulfillment via unsigned forged webhooks

Published Jul 24, 2026 · Updated Jul 24, 2026

Authorization bypass in Payment Plugins for Stripe WooCommerce 4.0.7 and earlier allows remote attackers to mark pending orders as paid. The webhook controller accepts a forged charge.pending event when the selected webhook secret is blank, trusts attacker-controlled order and gateway metadata, and calls payment_complete() with an attacker-supplied transaction ID. The default blank-secret state exposes pending asynchronous orders to unauthorized payment status changes and downstream fulfillment, while a configured non-empty Stripe webhook secret blocks the bypass.

CVSS severity5.3
Medium
EPSS probability0.35%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Authorization bypass in Payment Plugins for Stripe WooCommerce 4.0.7 and earlier allows remote attackers to mark pending orders as paid. The webhook controller accepts a forged charge.pending event when the selected webhook secret is blank, trusts attacker-controlled order and gateway metadata, and calls payment_complete() with an attacker-supplied transaction ID. The default blank-secret state exposes pending asynchronous orders to unauthorized payment status changes and downstream fulfillment, while a configured non-empty Stripe webhook secret blocks the bypass.

The record

CVE
CVE-2026-12654
Published
Jul 24, 2026
Updated
Jul 24, 2026
Vendor
Payment Plugins
Product
Payment Plugins for Stripe WooCommerce
Classifications
CWE-862, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jul 24, 2026CVE publishedPublication date reported by the CVE source.
  2. Jul 24, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <=4.0.7

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Payment Plugins · Payment Plugins for Stripe WooCommerceversion=0 <=4.0.7

Published CVSS scores

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

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-862Missing Authorization
T1190Exploit Public-Facing Application

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo