{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-5050 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-5050 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-5050 is a high-severity vulnerability in jconti Payment Gateway for Redsys \u0026 WooCommerce Lite, published on 16 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-5050 and fix it if it is affected.\n\nWhat it is: CVE-2026-5050 is a high-severity vulnerability in jconti Payment Gateway for Redsys \u0026 WooCommerce Lite, published on 16 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-5050 in the wild and no public exploit code.\n\nAffected product: jconti Payment Gateway for Redsys \u0026 WooCommerce Lite. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-5050/ (Markdown: https://insights.sbomify.com/CVE-2026-5050/index.md)","id":"CVE-2026-5050","markdown":"https://insights.sbomify.com/CVE-2026-5050/index.md","name":"CVE-2026-5050","record":{"aliases":["GHSA-6pcx-jf98-3w2h"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress payment plugin","requires_auth":"none","summary":"Unauthenticated attackers can bypass payment verification to mark orders as paid, enabling free product fulfillment in the Redsys WooCommerce plugin.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"The Payment Gateway for Redsys \u0026 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-08-03","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-08-03T01:49:40Z","kind":"github_poc","ref":"https://github.com/George0Papasotiriou/CVE-2026-5050-Blind-LDAP-Injection-via-Unescaped-Filter","stars":0,"title":null}],"tier":"poc_unverified"},"has_fix":null,"headline":"Security feature bypass in Payment Gateway for Redsys \u0026 WooCommerce Lite","id":"CVE-2026-5050","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Audit Log Plugin Directory Guard Bypass via Legacy path Option","id":"CVE-2026-5051"},"packages":[],"prev":{"headline":"Path traversal in Brocade SANnav","id":"CVE-2026-5049"},"products":["Payment Gateway for Redsys \u0026 WooCommerce Lite"],"published":"2026-04-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-16","vendors":["jconti"]},"summary":"Unauthenticated attackers can bypass payment verification to mark orders as paid, enabling free product fulfillment in the Redsys WooCommerce plugin.","url":"https://insights.sbomify.com/CVE-2026-5050/"}