CorvusPay WooCommerce Payment Gateway <= 2.7.4 - Missing Authorization to Unauthenticated Arbitrary Order Cancellation via 'order_number' Parameter
Strategic Overview
- Status
- Patched in 2.7.5
- Affected Plugin
- CorvusPay WooCommerce Payment Gateway
- Affected Version
<= 2.7.4- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-9028
At a glance
CVE-2026-9028 is a medium-severity Missing Authorization vulnerability in the CorvusPay WooCommerce Payment Gateway WordPress plugin, affecting versions <= 2.7.4. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.7.5; sites on affected versions should update now. Disclosed July 2026, reported by Valatty.
Vulnerability Overview
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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
Reaching this weakness in CorvusPay WooCommerce Payment Gateway <= 2.7.4 takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For CorvusPay WooCommerce Payment Gateway the fix is 2.7.5: builds <= 2.7.4 are affected, anything from 2.7.5 onward is not.
Remediation
Update to version 2.7.5, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: CorvusPay WooCommerce Payment Gateway 2.7.5 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in CorvusPay WooCommerce Payment Gateway
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C