Payment Gateway WordPress 插件(版本 2.2.0 及以下)未在使用共享密钥对银行支付通知回调进行身份验证之前,确保该密钥已正确配置。这导致未认证的攻击者能够伪造有效的支付通知,从而在共享密钥未设置的环境中将任意 WooCommerce 订单标记为“已支付”。此外,该回调接口还允许攻击者将任意处于“待处理”状态的订单标记为“失败”,无论共享密钥是否已配置。
Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
| Vendor | Product | Affected Versions | CPE | Subscribe |
|---|---|---|---|---|
| Unknown | Payment Gateway | 0 ~ 2.2.0 | - |
|
| # | POC Description | Source Link | Shenlong Link |
|---|
No public POC found.
Login to generate AI POC| CVE-2026-103300 | 5.3 MEDIUM | Eurobank WooCommerce Payment Gateway <= 2.1.1 - Unauthenticated Order Payment Forgery via |
| CVE-2026-111974 | 5.3 MEDIUM | GiveWP < 4.19.0.1 - Unauthenticated Donation Amount Restriction Bypass via Currency |
| CVE-2026-103319 | OPay Payment Gateway for WooCommerce <= 2.5.5 - Unauthenticated Payment Confirmation Forge | |
| CVE-2026-103381 | Mintpay <= 2.2.3 - Unauthenticated Order Payment Completion and Cancellation via Callback | |
| CVE-2026-103298 | CCAvenue Payment Gateway for WooCommerce <= 3.1 - Unauthenticated Order Payment Completion | |
| CVE-2026-103306 | iKhokha Payment Gateway < 3.0.4 - Unauthenticated Order Payment Forgery via Callback |