CVE-2026-9662: Recover Exit For WooCommerce (WordPress plugin) · PHP Remote File Inclusion
Affects Recover Exit For WooCommerce (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 8.1 High.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 9 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| plasmatizemediaRecover Exit For WooCommerce | Affected
| Fixed in– |
AI-suggested
Until an official fix is released, users should consider disabling the Recover Exit For WooCommerce plugin or restricting access to the vulnerable functionality. Avoid exposing the vulnerable endpoint to untrusted users. Monitor vendor channels for updates and apply patches promptly once available.
Description
The Recover Exit For WooCommerce WordPress plugin up to version 1.0.3 contains a Local File Inclusion vulnerability. This arises from insufficient validation of the user-controlled 'tpf' POST parameter used in an include() statement. Unauthenticated attackers can exploit this to perform path traversal and include unintended local PHP files, potentially exposing sensitive information and enabling code execution in some environments. The vulnerability is tracked as CVE-2026-9662 with a high severity score of 8.1. No official patch or remediation has been confirmed yet.
References
- wordfence.com/threat-intel/vulnerabilities/id/10552714-c8fb-455c-ad61-c0ef2db4b69f?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/recoverexit-for-woocommerce/trunk/recover_exit_main.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/recoverexit-for-woocommerce/tags/1.0.3/recover_exit_main.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/recoverexit-for-woocommerce/trunk/recover_exit_main.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/recoverexit-for-woocommerce/tags/1.0.3/recover_exit_main.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/recoverexit-for-woocommerce/trunk/recoverexit_woocommerce.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/recoverexit-for-woocommerce/tags/1.0.3/recoverexit_woocommerce.php (opens in a new tab)