Unauthenticated payment status manipulation via unchecked callback signatures
Published Apr 16, 2026 · Updated Apr 16, 2026
Signature verification failure in Payment Gateway for Redsys & WooCommerce Lite 7.0.0 and earlier allows remote attackers to mark orders paid. The Redsys, Bizum, and Google Pay successful_request() handlers compute a local signature but accept callback status without comparing it with Ds_Signature. Exploitation requires a valid order key and amount and can trigger checkout completion or fulfillment without a successful payment.
Summary
What happened
Signature verification failure in Payment Gateway for Redsys & WooCommerce Lite 7.0.0 and earlier allows remote attackers to mark orders paid. The Redsys, Bizum, and Google Pay successful_request() handlers compute a local signature but accept callback status without comparing it with Ds_Signature. Exploitation requires a valid order key and amount and can trigger checkout completion or fulfillment without a successful payment.
The record
- CVE
- CVE-2026-5050
- Published
- Apr 16, 2026
- Updated
- Apr 16, 2026
- Vendor
- José Conti
- Product
- Payment Gateway for Redsys & WooCommerce Lite
- Classifications
- CWE-347, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 16, 2026CVE publishedPublication date reported by the CVE source.
- Apr 16, 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 <=7.0.0
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