dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-40741

HIGH · 7.5 CVSS v3.1 Published 2026-06-15
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
Unauthenticated Broken Access Control in Redsys for WooCommerce Light <= 7.0.0 versions.

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 · low confidence

Unauthenticated Broken Access Control vulnerability in the Redsys payment gateway plugin for WooCommerce allows unauthenticated attackers to access functionality that should require authentication, potentially exposing sensitive payment operations or admin functions.

MitigationUpdate Redsys for WooCommerce Light to a version newer than 7.0.0; if immediate update is not possible, restrict access to the plugin's admin pages via server-level authentication or web application firewall rules.

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. Check if Redsys plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Redsys Gateway for WooCommerce' or 'Redsys for WooCommerce Light', or query the wp_plugins database table for plugins containing 'redsys' in the name or slug
    Affected if Redsys payment gateway plugin for WooCommerce is installed on the WordPress site
  2. Determine the installed version
    In WordPress admin plugins list, check the version column for the Redsys plugin, or read the plugin's main PHP file header (typically redsys-woocommerce.php or similar in wp-content/plugins/) which contains a 'Version:' field
    Affected if Installed version is 7.0.0 or earlier (versions up to and including 7.0.0 are affected)
  3. Inspect plugin admin access controls
    Attempt to access the Redsys plugin admin pages directly via browser without logging in (common paths include /wp-admin/admin.php?page=redsys* or /wp-admin/options-general.php?page=redsys*), or examine the plugin code for missing capability checks or nonces on admin AJAX handlers
    Affected if Admin plugin pages or AJAX endpoints are reachable without authentication or proper authorization checks
  4. Verify payment callback authentication
    Review plugin code for the payment notification/callback handlers (typically wc_api or webhook endpoints) and check if they validate user authentication before processing sensitive payment operations, or test by sending a request to the known callback URL without authentication credentials
    Affected if Payment gateway callback or notification endpoints process requests without requiring authentication

Environment is affected if Redsys for WooCommerce plugin version 7.0.0 or earlier is installed AND any admin functions or payment callback endpoints are accessible without authentication.

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

Update Redsys for WooCommerce Light to a version newer than 7.0.0; if immediate update is not possible, restrict access to the plugin's admin pages via server-level authentication or web application firewall rules.

Recommended fix Moderate confidence

Latest version of Redsys for WooCommerce Light (version > 7.0.0)

  1. 1. Navigate to WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Find 'Redsys for WooCommerce Light' in the plugin list
  4. 4. Check the current installed version number
  5. 5. If the installed version is 7.0.0 or lower, update the plugin to the latest available version via WordPress plugin repository or contact the plugin vendor for the patched version

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40741 — 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-40741 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