CVE-2026-5050

Payment Gateway for Redsys & WooCommerce Lite <= 7.0.0 - Improper Verification of Cryptographic Signature to Unauthenticated Payment Status Manipulation

2026-04-15 16:43
Nguyen Ngoc Duc (duc193)

Strategic Overview

Status
Patched in 7.0.1
Affected Version
<= 7.0.0
CVSS
7.5High
Weakness type
CWE-347 · Improper Verification of Cryptographic Signature
CVE
CVE-2026-5050
View all Payment Gateway for Redsys & WooCommerce Lite vulnerabilities

At a glance

CVE-2026-5050 is a high-severity Improper Verification of Cryptographic Signature vulnerability in the Payment Gateway for Redsys & WooCommerce Lite WordPress plugin, affecting versions <= 7.0.0. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. The issue is fixed in version 7.0.1; sites on affected versions should update now. Disclosed April 2026, reported by Nguyen Ngoc Duc (duc193).

Vulnerability Overview

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.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on integrity.

CWE-347: Improper Verification of Cryptographic Signature

The product does not verify, or incorrectly verifies, the cryptographic signature for data.

Remediation

Update to version 7.0.1, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Payment Gateway for Redsys & WooCommerce Lite 7.0.1 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Other vulnerabilities in Payment Gateway for Redsys & WooCommerce Lite

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C