Payment Gateway for Redsys & WooCommerce Lite <= 7.0.0 — Improper Verification of Cryptographic Signature to Unauthenticated Payment Status Manipulation
CVE-2026-5050Published · Updated Action summary
Affected: ≤7.0.0Update to 7.0.1 or newer
All remediation steps- Severity
- High7.5
- CVSS
- 7.5CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:NWhat does this vector mean?
AV:NAttack vector- Network
AC:LAttack complexity- Low
PR:NPrivileges required- None
UI:NUser interaction- None
S:UScope- Unchanged
C:NConfidentiality- None
I:HIntegrity- High
A:NAvailability- None
- Required access
- No account needed
- Exploit prediction (EPSS)
- No score
- CISA KEV
- Not listed
On this page8
Am I affected?
Payment Gateway for Redsys & WooCommerce Lite woo-redsys-gateway-light
- Affected≤ 7.0.0
- Patched in7.0.1
Update to 7.0.1 or newer.
You are affected if you run ≤ 7.0.0. Version 7.0.1 and later are not affected by this issue.
- Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Payment Gateway for Redsys & WooCommerce Lite.
- No admin access? Run a passive check of your site. It reads public files only.
- No account is needed to exploit this. Treat any exposed site on an affected version as at risk.
What to do
- Update to version 7.0.1, or a newer patched version
- Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
- Watch Payment Gateway for Redsys & WooCommerce Lite to get an email when the next vulnerability is published.
Advisory
Source description from Wordfence Intelligence, credited to Nguyen Ngoc Duc (duc193).
The Payment Gateway for Redsys & WooCommerce Lite plugin for WordPress is vulnerable to Improper Verification of Cryptographic Signature in versions up to, and including, 7.0.0 due to successful_request() handlers calculating a local signature but not validating Ds_Signature from the request before accepting payment status across the Redsys, Bizum, and Google Pay gateway flows. This makes it possible for unauthenticated attackers to forge payment callback data and mark pending orders as paid when they know a valid order key and order amount, potentially allowing checkout completion and product or service fulfillment without a successful payment.
Exploits & references
Proof-of-concept & detection
No public proof-of-concept or detection template is known for this vulnerability.
Advisories & patches
- Advisorywordfence.com
Related CVEs
More in Payment Gateway for Redsys & WooCommerce Lite
All 3| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium5.3 | Unauthenticated Payment Bypass ≤7.0.1Update to 7.0.2 | CVE-2026-12584 | |
| Medium5.3 | Missing Authorization ≤7.0.0Update to 7.0.1 | CVE-2026-40741 |
- Medium5.3Unauthenticated Payment Bypass
≤7.0.1Update to 7.0.2
- Medium5.3Missing Authorization
≤7.0.0Update to 7.0.1
Timeline
CVE published
Severity high, CVSS 7.5
Record last updated
Sources & licenses
Wordfence record- Vulnerability data
- Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
- CVE® identifiers
- Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
- CVSS / CWE
- National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
- VulnCrest content
- Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.