Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-6939 high CVSS 7.2

Cross-Site Scripting (XSS) in CorvusPay WooCommerce Payment Gateway (WordPress plugin) (CVE-2026-6939)

Summary

Cross-site scripting in CorvusPay WooCommerce Payment Gateway (WordPress plugin) (CVE-2026-6939). 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 Stored Cross-Site Scripting via the 'approval_code' parameter in all versions up to, and including, 2.7.4 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The unauthenticated REST endpoint POST /wp-json/corvuspay/success/ is registered with permission_callback set to __return_true, and although a signature validation step exists it only logs the result without halting execution, meaning an attacker can supply a completely arbitrary signature and have a malicious approval_code stored in the database unchallenged.

Source: NIST National Vulnerability Database 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-6939 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: 7.2/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-6939" on the vendor's site.

CVE-2026-6939 (CorvusPay WooCommerce Payment Gateway (WordPress plugin)) — CWE-79 / CVSS v3 7.2
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /wp-json/corvuspay/success/
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.

❓ What is the problem

Cross-site scripting (XSS) (CWE-79) exists in CorvusPay WooCommerce Payment Gateway (WordPress plugin). Attackers reach the vulnerable code path via POST /wp-json/corvuspay/success/ without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of CorvusPay WooCommerce Payment Gateway (WordPress plugin). Attack surface: POST /wp-json/corvuspay/success/.

🔥 Severity

Severity: High (CVSS 7.2/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

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

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで CorvusPay WooCommerce Payment Gateway (WordPress plugin) を使っているサービスとバージョンを洗い出す。

  2. 2
    Hunt 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 があれば該当パスのアラート発火履歴を確認。

  3. 3
    Post-deployment verification verify 
    Replay attack against POST /wp-json/corvuspay/success/ on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details