CVE-2026-103313

BitPay Gateway for WooCommerce <= 4.1.3 - Unauthenticated Payment Bypass via Payment Return Handler

Published Oct 28, 2026 CVSS 3.1 · 5.3 Medium EPSS < 1% KEV · Not listed
Description
The BitPay Gateway for WooCommerce WordPress plugin through 4.1.3 does not bind the payment provider's transaction confirmation to the order it completes, nor verify the confirmed amount, allowing an unauthenticated attacker who holds a single genuine low-value transaction to mark arbitrary higher-value orders as paid.

Analysis

AI-generated

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.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the BitPay Gateway for WooCommerce plugin to version 4.1.4 or later, which includes a binding check between transaction confirmations and orders.
  • If an update is not immediately possible, restrict the payment return handler to require authentication or a signed token confirming the order ID and amount.
  • Implement transaction monitoring to flag any orders marked as paid that exceed the transaction amount, and review logs for anomalous payment confirmations.
  • Consider disabling automatic order status changes until the merchant verifies the payment receipt manually.

Generated by OpenCVE AI on October 28, 2026 at 19:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Wordpress-extensions
Wordpress-extensions bitpay Gateway For Woocommerce
Vendors & Products Wordpress-extensions
Wordpress-extensions bitpay Gateway For Woocommerce
Type Values Removed Values Added
Weaknesses CWE-345
Type Values Removed Values Added
Weaknesses CWE-640
Type Values Removed Values Added
Description The BitPay Gateway for WooCommerce WordPress plugin through 4.1.3 does not bind the payment provider's transaction confirmation to the order it completes, nor verify the confirmed amount, allowing an unauthenticated attacker who holds a single genuine low-value transaction to mark arbitrary higher-value orders as paid.
Title BitPay Gateway for WooCommerce <= 4.1.3 - Unauthenticated Payment Bypass via Payment Return Handler
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N'}

Weaknesses
  • CWE-345

    Insufficient Verification of Data Authenticity

  • CWE-640

    Weak Password Recovery Mechanism for Forgotten Password

Sources

Status
PUBLISHED
Assigner
WPScan
Published
Updated
Oct 28, 2026, 5:48 PM
Reserved
Sep 30, 2026, 11:47 AM
Status
Deferred
Published
Oct 28, 2026, 11:17 AM
Modified
Oct 28, 2026, 6:17 PM