Get real-time updates on Telegram
CVE-2026-103299: Payment Gateway 0 through 2.2.0
CVE-2026-103299. CVSS 3.1 base score 5.3 (MEDIUM, Source advisory). EPSS 0.00137 (percentile 0.03059), scored 26-Oct-2026.
Affected technology
Payment Gateway · 0 through 2.2.0
Vendor not specified by the source
Description’s affected range: through 2.2.0 does not ensure a shared secret is configured before using it to authenticate the bank's payment-notification callback
Component: Not specified by the source
Attack conditions (Source advisory, CVSS 3.1): Network (remote) · No privileges required · No user interaction required
What an attacker can do
Unauthenticated attackers can forge a valid notification and mark any WooCommerce order as paid on installs where the secret has not been set, and the same callback lets them move any pending order to a failed state whether or not the secret is configured. Source advisory’s CVSS 3.1 assessment (base score 5.3/10) rates confidentiality and availability impact as none; integrity impact as low.
- CWE
- CWE-287
- CCR priority
- 21.2 /100 (P4)
- CVSS 3.1
- 5.3 /10 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N · Source advisory
- EPSS
- 0.00182 · percentile 0.07806 · 2026-11-15
- KEV
- no
Provenance
- FIRST EPSS daily exploit-probability · Source record · observed 2026-11-16 06:41:02.068004+00:00 UTC
- GitHub Advisory Database · Source record · observed 2026-11-07 13:45:04.855495+00:00 UTC
- NVD CVE API 2.0 · Source record · observed 2026-10-30 20:54:53.468690+00:00 UTC
Stable permalink: https://cybercodered.org/item/cve-cve-2026-103299.html