Description
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.
Published: 2026-07-09
Score: 5.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The CorvusPay WooCommerce Payment Gateway plugin for WordPress contains an improper verification of a cryptographic signature (CWE‑347). An unauthenticated attacker can POST to the /wp-json/corvuspay/success/ REST endpoint with an arbitrary or forged signature value; because the plugin logs the validation result but never checks it, the order is always marked as complete. This allows an attacker to obtain goods or services without payment, directly impacting merchant revenue and customer trust.

Affected Systems

Any WordPress site that installs the CorvusPay WooCommerce Payment Gateway plugin from corvusinfo, all versions up to and including 2.7.4, is susceptible. The flaw resides in the plugin code that handles the /wp-json/corvuspay/success/ endpoint and the order completion logic.

Risk and Exploitability

With a CVSS score of 5.3 the flaw is of moderate severity. The EPSS score indicates a low exploitation probability of less than 1%, and it is not listed in the CISA KEV catalog. The likely attack vector is an unauthenticated POST request to the success endpoint containing an arbitrary or forged signature and a valid order_number; 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.

Generated by OpenCVE AI on July 29, 2026 at 12:35 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the CorvusPay WooCommerce Payment Gateway to the latest release, which enforces signature validation before completing the order.
  • Modify the REST endpoint's permission_callback to require authentication, replacing the current '__return_true' that allows anyone to access the endpoint.
  • Implement firewall or reverse‑proxy rules to block unauthenticated POST requests to /wp-json/corvuspay/success/ until the plugin is updated.
  • Monitor order completion logs for transactions that lack a corresponding successful payment event and investigate discrepancies.

Generated by OpenCVE AI on July 29, 2026 at 12:35 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 09 Jul 2026 15:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Thu, 09 Jul 2026 10:45:00 +0000

Type Values Removed Values Added
Description 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.
Title CorvusPay WooCommerce Payment Gateway <= 2.7.4 - Unauthenticated Improper Verification of Cryptographic Signature to Payment Bypass via /wp-json/corvuspay/success/ REST Endpoint
Weaknesses CWE-347
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: Wordfence

Published:

Updated: 2026-07-09T14:39:29.620Z

Reserved: 2026-05-19T15:23:17.002Z

Link: CVE-2026-9027

cve-icon Vulnrichment

Updated: 2026-07-09T13:32:15.551Z

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-07-29T12:45:03Z

Weaknesses
  • CWE-347

    Improper Verification of Cryptographic Signature