CVE-2026-9662
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Recover Exit For WooCommerce plugin for WordPress is vulnerable to Local File Inclusion in versions up to 1.0.3. The vulnerability exists in the `recover_exit()` function where the `tpf` POST parameter is used directly in an `include()` statement without validation or sanitization. Unauthenticated attackers can exploit this via path traversal (e.g., `../../`) to include arbitrary local PHP files, potentially exposing sensitive information or achieving code execution depending on server configuration.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify the plugin is installedCheck the WordPress plugins directory for the 'recover-exit-for-woocommerce' folder, typically located at /wp-content/plugins/recover-exit-for-woocommerce/Affected if The plugin folder exists in the plugins directory
-
Determine the installed versionOpen the main plugin file (usually recover-exit-for-woocommerce.php) and locate the Version header in the plugin comment block, or search for a version constant defined in the plugin codeAffected if The version is 1.0.3 or lower, or if no version header is found and the plugin is present
-
Confirm the vulnerable code existsSearch the plugin source code for the recover_exit() function and verify it uses the tpf POST parameter in an include() or require() statement without sanitizationAffected if The code contains an include() or require() statement using $_POST['tpf'] without sanitizing the input
-
Check for exploitation attempts in logsReview web server access logs (Apache, Nginx, or reverse proxy) for POST requests to any plugin file that contain the tpf parameter with path traversal sequences such as ../Affected if Logs show POST requests with tpf parameter containing ../ sequences targeting the plugin endpoints
The environment is affected if the Recover Exit For WooCommerce plugin is installed with version 1.0.3 or lower and the vulnerable recover_exit() function handles the tpf parameter without input sanitization.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataDisable or remove the Recover Exit For WooCommerce plugin until a patched version is available from the vendor. If immediate removal is not feasible, restrict access to the affected endpoint at the web server or WAF level to mitigate exploitation.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9662 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-9662 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data