CVE-2026-6939 HIGH

CVE-2026-6939: CorvusPay WooCommerce Payment Gateway <= 2.7.4 - Unauthenticated Stored Cross-Site Scripting via 'approval_code' Parameter

Vendor Corvusinfo
Product CorvusPay WooCommerce Payment Gateway
Weakness CWE-79 · XSS
Published July 11, 2026
Last update July 13, 2026

CVSS base score

7.2/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction None
Confidentiality Low
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

CorvusPay WooCommerce Payment Gateway versions 2.7.4 and earlier contain a cross-site scripting (XSS) vulnerability that allows unauthenticated attackers to inject malicious scripts. The vulnerability can be exploited over the network without user interaction, affecting both the vulnerable component and other parts of the site. Site administrators should update to a version newer than 2.7.4.

What an attacker can do

03Attacker Capabilities

Inject malicious JavaScript that executes in visitors' browsers and affects other site components.

Potential impact on your site

04Site Impact

Visitors' browsers could execute attacker-controlled scripts, potentially stealing session tokens, payment data, or redirecting to phishing pages.

Conditions required to exploit

05Prerequisites

None. The attacker needs only network access; no authentication or user interaction required.

Key dates

06Disclosure timeline

July 11, 2026 CVE published
July 13, 2026 Record updated

Related vulnerabilities

08Related CVE