Technical impact
The BitPay Gateway for WooCommerce plugin releases that omit binding the payment provider's transaction confirmation to the specific order, and also fail to validate that the confirmed amount matches the order total. This flaw means an unauthenticated attacker who can generate a single low‑value, legitimate transaction can abuse the payment return handler to mark any higher‑value order as paid, effectively overriding the merchant's intended authorization process and allowing fraudulent revenue recognition.
Affected Systems
WordPress sites that use the BitPay Gateway for WooCommerce plugin, version 4.1.3 and earlier. The affected code resides in the plugin's payment return handler component, which is executed after the external payment confirmation returns. All installations of the plugin within that version range are potentially vulnerable if the merchant processes orders through the plugin.
Risk and Exploitability
The vulnerability is assigned a medium CVSS score of 5.3, with no publicly available EPSS score. It is not listed in the CISA KEV catalog, indicating no confirmed widespread exploitation yet. The likely attack vector is the payment return handler URL; an attacker needs only to perform a low‑value purchase to obtain a valid transaction reference, then craft a request to the return handler to expose a higher‑value order. Because the fix requires code changes, the exploitation is non‑trivial but feasible for attackers with access to the payment workflow. The monetary impact can be significant for merchants if not patched promptly.