PT-2026-56786 · WordPress · Corvuspay Woocommerce Payment Gateway
CVSS v3.1
5.3
Medium
| Vector | AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
Name of the Vulnerable Software and Affected Versions
CorvusPay WooCommerce Payment Gateway versions prior to 2.7.5
Description
An issue exists where the
corvuspay success handler function registers the REST endpoint POST /wp-json/corvuspay/success/ without proper authorization checks. Although the system calls $this->client->validate->signature() to verify the cryptographic signature, the result is only recorded in a debug log and not used to control the flow of execution. Consequently, the process always reaches the payment complete() function, allowing unauthenticated attackers to mark pending orders as paid by sending a request with a forged signature. Attackers can identify target orders using the order number parameter, as these IDs are sequential integers.Recommendations
Update CorvusPay WooCommerce Payment Gateway to version 2.7.5 or later.
As a temporary workaround, restrict access to the
POST /wp-json/corvuspay/success/ endpoint to prevent unauthorized requests.Fix
Improper Verification of Cryptographic Signature
Found an issue in the description? Have something to add? Feel free to write us 👾
Weakness Enumeration
Related Identifiers
Affected Products
Corvuspay Woocommerce Payment Gateway