Unauthenticated stored XSS via ignored signature failure
Published Jul 11, 2026 · Updated Jul 11, 2026
Stored XSS in CorvusPay WooCommerce Payment Gateway 2.7.4 and earlier allows remote attackers to execute scripts via approval_code. The public success REST route accepts any caller, logs a failed callback-signature check without stopping, and stores approval_code without adequate sanitization before later output. No authentication is required to plant the payload; execution occurs in a user's browser when affected order details or email content is viewed.
Summary
What happened
Stored XSS in CorvusPay WooCommerce Payment Gateway 2.7.4 and earlier allows remote attackers to execute scripts via approval_code. The public success REST route accepts any caller, logs a failed callback-signature check without stopping, and stores approval_code without adequate sanitization before later output. No authentication is required to plant the payload; execution occurs in a user's browser when affected order details or email content is viewed.
The record
- CVE
- CVE-2026-6939
- Published
- Jul 11, 2026
- Updated
- Jul 11, 2026
- Vendor
- Corvus Pay
- Product
- CorvusPay WooCommerce Payment Gateway
- Classifications
- CWE-79, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 11, 2026CVE publishedPublication date reported by the CVE source.
- Jul 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2.7.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo