Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify WooCommerce store with plugin
-
DeliverySend forged Coinbase webhook to endpoint
-
ExploitEmpty secret passes signature check
-
ExecutionOrder marked paid or cancelled
-
ImpactObtain goods free / disrupt orders
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V15 - Secure Coding and Architecture Data authenticity verification
|
| Exploitation Conditions | Exploitation requires that the plugin's Coinbase Commerce webhook shared secret is left empty, which is the DEFAULT state - the plugin does not reject an unconfigured secret, so any store that has not manually set a valid secret is vulnerable out of the box. The attacker needs network reachability to the public webhook endpoint and knowledge or guessing of a target order ID; no authentication, credentials, or user interaction are required (PR:N/UI:N). The primary limiting factor is that a merchant who has explicitly configured a non-empty, correct shared secret would cause forged notifications to fail signature validation, mitigating the issue; impact is also bounded to WooCommerce order payment status (mark-paid or cancel) rather than full site compromise. |
| Impact | This is a genuine but moderate-severity risk rather than a critical priority. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) correctly reflects that a remote, unauthenticated attacker can trigger the flaw over the network with low complexity and no user interaction, which is confirmed by the root cause: webhook signature validation is effectively disabled because the shared secret is empty by default and an unconfigured secret is not rejected. However, the score is held to 5.3 by the limited impact (C:N/I:L/A:N, scope unchanged) - the attacker manipulates WooCommerce order payment state rather than achieving code execution or data theft. A public proof-of-concept exists (WPScan), raising practical exploitability, but there is NO CISA KEV listing and NO EPSS score in the provided data, so there is no evidence of active or widespread exploitation - this signals an opportunistic/targeted fraud risk against individual stores rather than mass exploitation at this time. The main judgement caveat: CVSS rates impact as only I:L, but the business consequence (marking unpaid orders as paid to obtain goods for free, or cancelling legitimate paid orders) can be financially significant for the affected merchant despite the modest numeric score. |
| Exploit ScenarioDerived | An attacker identifies a WooCommerce store running this plugin with the default (empty) webhook secret, places or targets an order, then sends a forged Coinbase Commerce webhook notification directly to the store's webhook endpoint. Because the empty shared secret is not rejected, the forged signature passes validation and the order is marked 'paid,' letting the attacker receive goods or services without payment; the same technique can cancel already-paid orders to disrupt the merchant. A public PoC from WPScan lowers the skill required to carry this out. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 19, 2026
Forged Coinbase Commerce webhook notifications can mark arbitrary WooCommerce orders as paid or cancel already-paid orders in the Coinbase Commerce Payment Gateway plugin through version 1.4.1. The plugin ships with an empty webhook shared secret and does not reject an unconfigured value, so unauthenticated remote attackers who know or guess an order ID can bypass signature validation; publicly available exploit code exists. The CVSS 5.3 impact is limited to order-payment integrity with no confidentiality or availability impact, and merchants who have explicitly set a non-empty shared secret are not affected by the bypass.
RemediationAI
No vendor-released patch identified at time of analysis; confirm the current fixed release with the plugin vendor or the WPScan advisory before upgrading beyond 1.4.1. The effective mitigation is to configure a strong, unique, non-empty shared secret in the plugin's Coinbase Commerce webhook settings and ensure it matches the secret in the Coinbase Commerce dashboard, because a correct secret causes forged signatures to fail validation. If a fix is not yet available, disable the Coinbase Commerce gateway plugin until an update is released, restrict the webhook endpoint at the WAF or reverse proxy to Coinbase Commerce source ranges (trade-off: Coinbase IP changes can cause false blocks and break legitimate payment notifications), and audit recent WooCommerce orders for unexpected paid or cancelled status changes. Consult https://wpscan.com/vulnerability/3d43ae6a-ca0d-49f9-aa3a-a584e5155efe/ for updated fix information.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The plugin is a WordPress/WooCommerce payment gateway that accepts asynchronous payment callbacks from Coinbase Commerce. It authenticates those callbacks by computing an HMAC-style signature over the raw request body with a merchant-configured shared secret and comparing it to the signature header; however, the secret is empty by default and the webhook handler does not reject an unconfigured secret, so an attacker can generate a valid signature for an arbitrary forged payload using the empty key. The CPE cpe:2.3:a:unknown:coinbase_commerce_payment_gateway_for_woocommerce:*:*:*:*:*:*:*:* identifies the affected WordPress plugin across all versions through 1.4.1; no CWE is assigned, but the root-cause class is missing or improper verification of a cryptographic signature for a security-critical operation (order status change). Because the handler is network-reachable and processes unauthenticated POSTs, a forged event such as charge:confirmed or charge:failed can transition a chosen order to paid or cancelled. The impact is confined to WooCommerce order state; no code execution, file access, or data disclosure is described.
Know when Coinbase Commerce Payment Gateway For Woocommerce gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Remote unauthenticated webhook forgery works against the default empty-secret config (AV:N/AC:L/PR:N/UI:N); impact is limited order-state modification (I:L) with no confidentiality or availability loss.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
DescriptionCVE.org
The Coinbase Commerce Payment Gateway for WooCommerce WordPress plugin through 1.4.1 does not verify the authenticity of incoming payment webhook notifications, because the shared secret used to validate the request signature is empty by default and nothing rejects an unconfigured secret, allowing unauthenticated attackers to forge notifications that mark arbitrary orders as paid or cancel already-paid orders.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
EUVD-2026-104095
GHSA-cx3h-5fq4-rp7v
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB