{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-9027 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-9027 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-9027 is a medium-severity vulnerability in corvusinfo CorvusPay WooCommerce Payment Gateway, published on 9 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-9027 and fix it if it is affected.\n\nWhat it is: CVE-2026-9027 is a medium-severity vulnerability in corvusinfo CorvusPay WooCommerce Payment Gateway, published on 9 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-9027 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-9027/ (Markdown: https://insights.sbomify.com/CVE-2026-9027/index.md)","id":"CVE-2026-9027","markdown":"https://insights.sbomify.com/CVE-2026-9027/index.md","name":"CVE-2026-9027","record":{"aliases":["GHSA-g5m6-f674-9758"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify","other"],"network_reachable":"yes","non_default_config":false,"product_category":"WooCommerce payment plugin","requires_auth":"none","summary":"Unauthenticated attackers can bypass payment verification to mark orders as paid, obtaining goods without payment.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"The CorvusPay WooCommerce Payment Gateway plugin for WordPress is vulnerable to Payment Bypass via Improper Verification of Cryptographic Signature in all versions up to, and including, 2.7.4. The `corvuspay_success_handler` function registers the REST endpoint `POST /wp-json/corvuspay/success/` with `'permission_callback' =\u003e '__return_true'`, and while it calls `$this-\u003eclient-\u003evalidate-\u003esignature()` and stores the boolean result in `$res`, the result is never evaluated in a conditional — it is only written to the debug log — causing execution to unconditionally reach `$order-\u003epayment_complete()` regardless of whether the cryptographic signature is valid. This makes it possible for unauthenticated attackers to mark any pending WooCommerce order as fully paid by sending a POST request to the success endpoint containing an arbitrary or forged signature value, allowing them to obtain goods or services without payment. Because WooCommerce order IDs are sequential integers, target orders are trivially enumerable via the `order_number` POST parameter, requiring no prior knowledge of the victim order.","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":"Security feature bypass in CorvusPay WooCommerce Payment Gateway","id":"CVE-2026-9027","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"Missing authorization in CorvusPay WooCommerce Payment Gateway","id":"CVE-2026-9028"},"packages":[],"prev":{"headline":"Cross-site scripting in DELMIA Service Process Engineer","id":"CVE-2026-9024"},"products":["CorvusPay WooCommerce Payment Gateway"],"published":"2026-07-09","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-09","vendors":["corvusinfo"]},"summary":"Unauthenticated attackers can bypass payment verification to mark orders as paid, obtaining goods without payment.","url":"https://insights.sbomify.com/CVE-2026-9027/"}