dbcve.org
Improper Signature VerificationWeakness · CWE-347

CVE-2026-5050

HIGH · 7.5 CVSS v3.1 Published 2026-04-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Payment Gateway for Redsys & WooCommerce Lite plugin fails to validate the Ds_Signature cryptographic signature in payment callback requests. The successful_request() handlers calculate a local signature but do not verify the incoming Ds_Signature parameter before accepting payment status, allowing unauthenticated attackers to forge callbacks and mark orders as paid without actual payment.

MitigationUpgrade to version 7.0.1 or later which includes proper Ds_Signature validation. Until patched, consider disabling the Redsys, Bizum, and Google Pay gateway flows or implementing additional server-side verification.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find 'Payment Gateway for Redsys & WooCommerce Lite' (or 'Redsys Lite'), then read the version number from the plugin description. Alternatively, check the main plugin PHP file header for 'Version:' or check readme.txt
    Affected if The installed version is below 7.0.1 (no patch version specified, so any version before the fix) or if the version cannot be determined and the plugin is active
  2. Verify WooCommerce is active
    Confirm WooCommerce plugin is installed and active in your WordPress environment, as this plugin is a WooCommerce payment gateway extension
    Affected if WooCommerce is active and the Redsys gateway plugin is installed - the vulnerable callback handlers only process requests when WooCommerce processes payment callbacks
  3. Confirm the Redsys gateway is enabled
    Go to WooCommerce > Settings > Payments (or Payments tab) and check if 'Redsys' or 'Redsys Payment Gateway' is enabled among available payment methods
    Affected if The Redsys gateway is enabled and configured - the vulnerability only affects environments where the Redsys payment gateway is active and able to receive callback requests
  4. Check if the gateway receives callback requests
    Review server access logs for POST requests to /?wc-api=wc_redsys_gateway or similar Redsys callback endpoints (often containing 'Ds_Signature' or 'Ds_Response' parameters in the request)
    Affected if Your server is publicly accessible and receives callback POST requests from Redsys - this is the attack vector for forging payment confirmations

Your environment is affected if the Payment Gateway for Redsys & WooCommerce Lite plugin version is below 7.0.1, WooCommerce is active, the Redsys gateway is enabled, and your server can receive callback requests from the payment processor.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 7.0.1 or later which includes proper Ds_Signature validation. Until patched, consider disabling the Redsys, Bizum, and Google Pay gateway flows or implementing additional server-side verification.

Recommended fix Moderate confidence

Upgrade to the latest version available in the WordPress plugin repository (version higher than 7.0.0)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Payment Gateway for Redsys & WooCommerce Lite' plugin
  4. 4. Check the current installed version number
  5. 5. If the installed version is 7.0.0 or below, update the plugin to the latest version available in the WordPress plugin repository
  6. 6. After updating, verify the new version number reflects the update
Caveat Review plugin settings and test payment flows after upgrade to ensure compatibility with your WooCommerce setup

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-5050 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-5050 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data