{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-9662 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-9662 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-9662 is a high-severity path traversal vulnerability in plasmatizemedia Recover Exit For WooCommerce, published on 9 Jun 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-9662 and fix it if it is affected.\n\nWhat it is: CVE-2026-9662 is a high-severity path traversal vulnerability in plasmatizemedia Recover Exit For WooCommerce, published on 9 Jun 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-9662 in the wild and no public exploit code.\n\nAffected product: plasmatizemedia Recover Exit 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-9662/ (Markdown: https://insights.sbomify.com/CVE-2026-9662/index.md)","id":"CVE-2026-9662","markdown":"https://insights.sbomify.com/CVE-2026-9662/index.md","name":"CVE-2026-9662","record":{"aliases":["GHSA-m9vh-97x5-pc68"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can exploit path traversal in the Recover Exit For WooCommerce plugin to include local files, potentially exposing sensitive data or executing code.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-98","name":"Improper Control of Filename for Include/Require Statement in PHP Program"}],"description":"The Recover Exit For WooCommerce plugin for WordPress is vulnerable to Local File Inclusion in all versions up to and including 1.0.3. This is due to insufficient validation and sanitization of the user-controlled `tpf` POST parameter before it is used in an `include()` path in the `recover_exit()` function. This makes it possible for unauthenticated attackers to perform path traversal and include unintended local PHP files, which can lead to sensitive information exposure and, in certain deployment chains, code execution.","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":"Recover Exit For WooCommerce \u003c= 1.0.3 - Unauthenticated Local File Inclusion via 'tpf' Parameter","id":"CVE-2026-9662","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"IBM WebSphere Application Server prior to 9.0.5.29 and 8.5.5.31 are affected by multiple vulnerabilities","id":"CVE-2026-9667"},"packages":[],"prev":{"headline":"Multiple exploitable stack-based buffer overflow vulnerabilities exist in the boa formFilter functionality of X2000R (version(s): TOTOLINK-X","id":"CVE-2026-9660"},"products":["Recover Exit For WooCommerce"],"published":"2026-06-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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-06-09","vendors":["plasmatizemedia"]},"summary":"Unauthenticated attackers can exploit path traversal in the Recover Exit For WooCommerce plugin to include local files, potentially exposing sensitive data or executing code.","url":"https://insights.sbomify.com/CVE-2026-9662/"}