WordPress security by component
CorvusPay WooCommerce Payment Gateway
Plugin description
CorvusPay WooCommerce Payment Gateway is a WordPress component with 4 published CVE records in this archive. The latest tracked vulnerability was published Jul 11, 2026; the highest CVE/CNA score is 7.5.
Plugin slug:
corvuspay-woocommerce-integrationLatest vulnerability
CVE-2026-6939: CorvusPay WooCommerce Payment Gateway: Cross-site scripting
CorvusPay WooCommerce Payment Gateway is affected by cross-site scripting. The vulnerable path is reachable without authentication. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The published affected range is <= 2.7.4.
| Safe version |
|
||
|---|---|---|---|
| Jul 11, 2026 |
CVE-2026-6939
CorvusPay WooCommerce Payment Gateway: Cross-site scripting
CorvusPay WooCommerce Payment Gateway is affected by cross-site scripting. The vulnerable path is reachable without authentication. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The published affected range is <= 2.7.4.
|
> 2.7.4 |
CVE7.2
NVDPending
|
| Jul 09, 2026 |
CVE-2026-9028
CorvusPay WooCommerce Payment Gateway: A security weakness
CorvusPay WooCommerce Payment Gateway is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is <= 2.7.4.
|
> 2.7.4 |
CVE5.3
NVDPending
|
| Jul 09, 2026 |
CVE-2026-9027
CorvusPay WooCommerce Payment Gateway: A security weakness
CorvusPay WooCommerce Payment Gateway is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is <= 2.7.4.
|
> 2.7.4 |
CVE5.3
NVDPending
|
| Jun 26, 2026 |
CVE-2026-56029
CorvusPay WooCommerce Payment Gateway: A security weakness
CorvusPay WooCommerce Payment Gateway is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is n/a through 2.7.4.
|
2.7.5 |
CVE7.5
NVDPending
|