Vulnerability in CorvusPay WooCommerce Payment Gateway (WordPress plugin) (CVE-2026-9027)
Summary
Vulnerability in CorvusPay WooCommerce Payment Gateway (WordPress plugin) (CVE-2026-9027). Risk of unauthorized operations or information disclosure. Exploitable via POST /wp-json/corvuspay/success/.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-9027 has been found in CorvusPay WooCommerce Payment Gateway (WordPress plugin).
Attackers can target a specific entry point like POST /wp-json/corvuspay/success/ over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "CorvusPay WooCommerce Payment Gateway (WordPress plugin) CVE-2026-9027" on the vendor's site.
CVE-2026-9027 (CorvusPay WooCommerce Payment Gateway (WordPress plugin)) — CWE-347 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /wp-json/corvuspay/success/ / corvuspay_success_handler / order_number
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-347) exists in CorvusPay WooCommerce Payment Gateway (WordPress plugin). Attackers reach the vulnerable code path via POST /wp-json/corvuspay/success/ without authentication.
Check the vendor advisory for the affected versions of CorvusPay WooCommerce Payment Gateway (WordPress plugin). Attack surface: POST /wp-json/corvuspay/success/ / corvuspay_success_handler / order_number.
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /wp-json/corvuspay/success/ requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで CorvusPay WooCommerce Payment Gateway (WordPress plugin) を使っているサービスとバージョンを洗い出す。
-
2Hunt for indicators of compromise detect
grep 'POST /wp-json/corvuspay/success/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /wp-json/corvuspay/success/への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against POST /wp-json/corvuspay/success/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。