{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-0692 exists.","fix":"No fix has been published for CVE-2026-0692 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-0692 is a high-severity missing authorization vulnerability in BlueSnap Payment Gateway for WooCommerce, published on 14 Feb 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-0692 and fix it if it is affected.\n\nWhat it is: CVE-2026-0692 is a high-severity missing authorization vulnerability in BlueSnap Payment Gateway for WooCommerce, published on 14 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-0692 exists.\n\nAffected product: BlueSnap Payment Gateway for WooCommerce. 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-0692/ (Markdown: https://insights.sbomify.com/CVE-2026-0692/index.md)","id":"CVE-2026-0692","markdown":"https://insights.sbomify.com/CVE-2026-0692/index.md","name":"CVE-2026-0692","record":{"aliases":["GHSA-xh3r-gpf9-2v95"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can bypass IP restrictions to forge payment notifications and manipulate order statuses in the BlueSnap WooCommerce plugin.","user_interaction":"not_required","vuln_class":"missing_authorization"},"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-862","name":"Missing Authorization"}],"description":"The BlueSnap Payment Gateway for WooCommerce plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 3.4.0. This is due to the plugin relying on WooCommerce's `WC_Geolocation::get_ip_address()` function to validate IPN requests, which trusts user-controllable headers like X-Real-IP and X-Forwarded-For to determine the client IP address. This makes it possible for unauthenticated attackers to bypass IP allowlist restrictions by spoofing a whitelisted BlueSnap IP address and send forged IPN (Instant Payment Notification) data to manipulate order statuses (mark orders as paid, failed, refunded, or on-hold) without proper authorization.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2026/CVE-2026-0692.yaml","stars":null,"title":"BlueSnap Payment Gateway for WooCommerce \u003c=3.4.0 - IPN Authorization Bypass"}],"tier":"weaponised"},"has_fix":null,"headline":"Missing authorization in BlueSnap Payment Gateway for WooCommerce","id":"CVE-2026-0692","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site scripting in Allow HTML in Category Descriptions","id":"CVE-2026-0693"},"packages":[],"prev":{"headline":"CM E-Mail Blacklist \u003c= 1.6.2 - Authenticated (Administrator+) Stored Cross-Site Scripting via 'black_email' Parameter","id":"CVE-2026-0691"},"products":["BlueSnap Payment Gateway for WooCommerce"],"published":"2026-02-14","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":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["bluesnap"]},"summary":"Unauthenticated attackers can bypass IP restrictions to forge payment notifications and manipulate order statuses in the BlueSnap WooCommerce plugin.","url":"https://insights.sbomify.com/CVE-2026-0692/"}