Bitpay Gateway For Woocommerce
Monthly
Unauthenticated attackers can mark arbitrary high-value WooCommerce orders as paid on any store running the BitPay Gateway for WooCommerce plugin through version 4.1.3, because the plugin accepts a payment-provider transaction confirmation without checking that it belongs to the order being completed or that the confirmed amount matches the order total. The only prerequisite is that the site has the BitPay payment method active and that the attacker possesses one genuine - even very low-value - BitPay transaction to reuse as the confirmation. Impact is limited to payment-status falsification (integrity) rather than site takeover or data exposure, and a public proof-of-concept reference exists (the WPScan advisory entry); it is not verified as working exploit code, no CISA KEV entry is recorded, and vuln.today schedules this at this_month priority rather than act_now.
Unauthenticated attackers can mark arbitrary high-value WooCommerce orders as paid on any store running the BitPay Gateway for WooCommerce plugin through version 4.1.3, because the plugin accepts a payment-provider transaction confirmation without checking that it belongs to the order being completed or that the confirmed amount matches the order total. The only prerequisite is that the site has the BitPay payment method active and that the attacker possesses one genuine - even very low-value - BitPay transaction to reuse as the confirmation. Impact is limited to payment-status falsification (integrity) rather than site takeover or data exposure, and a public proof-of-concept reference exists (the WPScan advisory entry); it is not verified as working exploit code, no CISA KEV entry is recorded, and vuln.today schedules this at this_month priority rather than act_now.