CVE-2026-9027: CWE-347 Improper Verification of Cryptographic Signature in corvusinfo CorvusPay WooCommerce Payment Gateway
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.
AI Analysis
Technical Summary
CVE-2026-9027 describes an improper verification of cryptographic signature vulnerability (CWE-347) in the CorvusPay WooCommerce Payment Gateway plugin for WordPress. The plugin registers a REST endpoint POST /wp-json/corvuspay/success/ with an open permission callback, allowing unauthenticated access. Although the endpoint calls a signature validation function and logs the result, it does not act on the validation outcome. Consequently, the order payment is marked complete regardless of signature validity. Because WooCommerce order IDs are sequential, attackers can enumerate order numbers and forge payment completions, enabling payment bypass and unauthorized acquisition of goods or services.
Potential Impact
An attacker can mark any pending WooCommerce order as paid without providing a valid cryptographic signature or authenticating, resulting in unauthorized order completion. This leads to potential financial loss for merchants as goods or services may be delivered without actual payment. The vulnerability does not impact confidentiality or availability but compromises the integrity of the payment process.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, it is recommended to disable or restrict access to the vulnerable REST endpoint if possible, or implement custom validation to ensure signature verification results are enforced before marking orders as paid. Monitor vendor channels for updates and apply official patches promptly once released.
CVE-2026-9027: CWE-347 Improper Verification of Cryptographic Signature in corvusinfo CorvusPay WooCommerce Payment Gateway
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.
CVSS v3.1
Score 5.3medium
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-9027 describes an improper verification of cryptographic signature vulnerability (CWE-347) in the CorvusPay WooCommerce Payment Gateway plugin for WordPress. The plugin registers a REST endpoint POST /wp-json/corvuspay/success/ with an open permission callback, allowing unauthenticated access. Although the endpoint calls a signature validation function and logs the result, it does not act on the validation outcome. Consequently, the order payment is marked complete regardless of signature validity. Because WooCommerce order IDs are sequential, attackers can enumerate order numbers and forge payment completions, enabling payment bypass and unauthorized acquisition of goods or services.
Potential Impact
An attacker can mark any pending WooCommerce order as paid without providing a valid cryptographic signature or authenticating, resulting in unauthorized order completion. This leads to potential financial loss for merchants as goods or services may be delivered without actual payment. The vulnerability does not impact confidentiality or availability but compromises the integrity of the payment process.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, it is recommended to disable or restrict access to the vulnerable REST endpoint if possible, or implement custom validation to ensure signature verification results are enforced before marking orders as paid. Monitor vendor channels for updates and apply official patches promptly once released.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-05-19T15:23:17.002Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a4f798068715ace43289539
Added to database: 07/09/2026, 10:35:44 UTC
Last enriched: 07/09/2026, 10:48:22 UTC
Last updated: 08/23/2026, 10:52:11 UTC
Views: 83
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.