{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-6939 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-6939 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-6939 is a high-severity cross-site scripting vulnerability in corvusinfo CorvusPay WooCommerce Payment Gateway, published on 11 Jul 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-6939 and fix it if it is affected.\n\nWhat it is: CVE-2026-6939 is a high-severity cross-site scripting vulnerability in corvusinfo CorvusPay WooCommerce Payment Gateway, published on 11 Jul 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-6939 in the wild and no public exploit code.\n\nAffected product: corvusinfo CorvusPay WooCommerce Payment Gateway. 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-6939/ (Markdown: https://insights.sbomify.com/CVE-2026-6939/index.md)","id":"CVE-2026-6939","markdown":"https://insights.sbomify.com/CVE-2026-6939/index.md","name":"CVE-2026-6939","record":{"aliases":["GHSA-3qh5-q7jr-f3w8"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress payment plugin","requires_auth":"none","summary":"Unauthenticated attackers can inject arbitrary scripts via the approval_code parameter in the CorvusPay WooCommerce plugin, leading to stored XSS.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"The CorvusPay WooCommerce Payment Gateway plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'approval_code' parameter in all versions up to, and including, 2.7.4 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The unauthenticated REST endpoint POST /wp-json/corvuspay/success/ is registered with permission_callback set to __return_true, and although a signature validation step exists it only logs the result without halting execution, meaning an attacker can supply a completely arbitrary signature and have a malicious approval_code stored in the database unchallenged.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Cross-site scripting in CorvusPay WooCommerce Payment Gateway","id":"CVE-2026-6939","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":11,"next":{"headline":"radare2 \u003c 6.1.4 Project Deletion Path Traversal Directory Deletion","id":"CVE-2026-6940"},"packages":[],"prev":{"headline":"IBM® Db2® is vulnerable to authorization bypass when uploading to a remote object storage path with a special query","id":"CVE-2026-6938"},"products":["CorvusPay WooCommerce Payment Gateway"],"published":"2026-07-11","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)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-13","vendors":["corvusinfo"]},"summary":"Unauthenticated attackers can inject arbitrary scripts via the approval_code parameter in the CorvusPay WooCommerce plugin, leading to stored XSS.","url":"https://insights.sbomify.com/CVE-2026-6939/"}