# CVE-2026-9662: Recover Exit For WooCommerce <= 1.0.3 - Unauthenticated Local File Inclusion via 'tpf' Parameter

> Unauthenticated attackers can exploit path traversal in the Recover Exit For WooCommerce plugin to include local files, potentially exposing sensitive data or executing code.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jun 2026
- **Updated:** 9 Jun 2026
- **Also known as:** GHSA-m9vh-97x5-pc68

## What is CVE-2026-9662?

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.

### Official 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.

Weakness: CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program)

## Which versions are affected by CVE-2026-9662?


## How do I fix CVE-2026-9662?

No fix has been published for CVE-2026-9662 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-9662 being exploited?

There is no known exploitation of CVE-2026-9662 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-9662 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2026-9662 in the wild and no public exploit code.

Affected product: plasmatizemedia Recover Exit For WooCommerce. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-9662/ (Markdown: https://insights.sbomify.com/CVE-2026-9662/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-9662
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-9662
- OSV: https://osv.dev/vulnerability/CVE-2026-9662

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-9662/
Summaries are generated and may contain mistakes; the official description above is the record.