Skip to content
Fencer Vulns
high 8.1

CVE-2020-8819 json

CardGate Payments plugin for WooCommerce does not validate request origin

published 2020-02-25 6 y ago modified 2026-06-17 4 mo ago also GHSA-5pq5-9phv-q5j3 , EUVD-2022-2632

cvss
8.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
4.9%
EPSS 4.9% chance of exploitation in 30 days, percentile 92%
public exploits
1
Exploit-DB

Summary

An issue was discovered in the CardGate Payments plugin through 3.1.15 for WooCommerce. Lack of origin authentication in the IPN callback processing function in cardgate/cardgate.php allows an attacker to remotely replace critical plugin settings (merchant ID, secret key, etc.) and therefore bypass the payment process (e.g., spoof an order status by manually sending an IPN callback request with a valid signature but without real payment) and/or receive all of the subsequent payments.

Patch / fix

  • packagist cardgate/woocommerce 3.1.16

Timeline

  1. First public exploit (EDB-48134)
  2. Published

Exploit prediction

4.88% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • EDB-48134 WordPress Plugin WooCommerce CardGate Payment Gateway 3.1.15 - Payment Process Bypass webapps, 2020-02-25
  • github.com https://github.com/cardgate/woocommerce/blob/f2111af7b1a3fd701c1c5916137f3ac09482feeb/cardgate/cardgate.php#L426-L442 referenced PoC, tagged "exploit" by a source, unverified
  • github.com https://github.com/cardgate/woocommerce/issues/18 referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com http://packetstormsecurity.com/files/156504/WordPress-WooCommerce-CardGate-Payment-Gateway-3.1.15-Bypass.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
NVD 2.0 5.5 AV:N/AC:L/Au:S/C:P/I:P/A:N
GitHub 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
packagist cardgate/woocommerce
<3.1.16
3.1.16

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.