HomeWordPress vulnerabilitiesCorvusPay WooCommerce Payment Gateway
CorvusPay WooCommerce Payment Gateway vulnerabilities
CorvusPay WooCommerce Payment Gateway has 3 known vulnerabilities in this database. The most recent published record is dated 11 Jul 2026.
- Known vulnerabilities
- 3
- Active installs
- 1,000+
- Latest version
- 2.7.6
- Last updated
- 17 Jul 2026
- Most recent
- 11 Jul 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-6939 | High 7.2 | Up to 2.7.4 | Fixed in a later version (latest 2.7.6) | 11 Jul 2026 |
| Security weakness CVE-2026-9027 | Medium 5.3 | Up to 2.7.4 | Fixed in a later version (latest 2.7.6) | 9 Jul 2026 |
| Broken access control CVE-2026-9028 | Medium 5.3 | Up to 2.7.4 | Fixed in a later version (latest 2.7.6) | 9 Jul 2026 |
Read the published descriptions
- CVE-2026-6939, 11 Jul 2026
- The CorvusPay WooCommerce Payment Gateway plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'approval_code' parameter in all versions up to, and including, 2.7.4 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The unauthenticated REST endpoint POST /wp-json/corvuspay/success/ is registered with permission_callback set to __return_true, and although a signature validation step exists it only logs the result without halting execution, meaning an attacker can supply a completely arbitrary signature and have a malicious approval_code stored in the database unchallenged. CVE record
- CVE-2026-9027, 9 Jul 2026
- The CorvusPay WooCommerce Payment Gateway plugin for WordPress is vulnerable to Payment Bypass via Improper Verification of Cryptographic Signature in all versions up to, and including, 2.7.4. The `corvuspay_success_handler` function registers the REST endpoint `POST /wp-json/corvuspay/success/` with `'permission_callback' => '__return_true'`, and while it calls `$this->client->validate->signature()` and stores the boolean result in `$res`, the result is never evaluated in a conditional - it is only written to the debug log - causing execution to unconditionally reach `$order->payment_complete()` regardless of whether the cryptographic signature is valid. This makes it possible for unauthenticated attackers to mark any pending WooCommerce order as fully paid by sending a POST request to the success endpoint containing an arbitrary or forged signature value, allowing them to obtain goods or services without payment. Because WooCommerce order IDs are sequential integers, target orders are trivially enumerable via the `order_number` POST parameter, requiring no prior knowledge of the victim order. CVE record
- CVE-2026-9028, 9 Jul 2026
- The CorvusPay WooCommerce Payment Gateway plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 2.7.4. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to cancel any WooCommerce order placed via the CorvusPay payment method by supplying an arbitrary order number to the /wp-json/corvuspay/cancel/ REST endpoint. CVE record
What to do if you run CorvusPay WooCommerce Payment Gateway
If you run CorvusPay WooCommerce Payment Gateway, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new CorvusPay WooCommerce Payment Gateway vulnerabilities
Free. We email you when a new vulnerability is published for CorvusPay WooCommerce Payment Gateway, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.