Analyst readout for executives and security teams
Plain-English summary
A WooCommerce add-on can let an unauthenticated internet user make WordPress include unintended local PHP files. On affected stores, this can expose sensitive data and, depending on server configuration and file contents, may support code execution. The issue is high severity, but the CVSS vector marks attack complexity as high.
Executive priority
Treat this as urgent for any public WooCommerce site using the plugin. Prioritize inventory and temporary removal because unauthenticated access is enough to reach the vulnerable behavior, and no fixed version is identified in the provided sources.
Technical view
Recover Exit For WooCommerce through 1.0.3 insufficiently validates the user-controlled POST parameter `tpf` before using it in an `include()` path inside `recover_exit()`. The CVE maps this to CWE-98. The reported impact is local file inclusion with high confidentiality, integrity, and availability impact under certain deployment chains.
Likely exposure
Exposure is limited to WordPress sites running Recover Exit For WooCommerce versions up to and including 1.0.3, especially public WooCommerce sites. The source bundle does not identify a fixed version or confirm broader product impact.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. Exploitation is unauthenticated and network-reachable, but rated high complexity, likely because useful impact depends on local files and deployment conditions.
Researcher notes
Primary evidence is the CVE description, Wordfence advisory reference, and WordPress Trac source references around the `recover_exit()` logic. The bundle supports LFI through `tpf`; it does not provide exploit telemetry, proof of active exploitation, or a named patched release.
Mitigation direction
- Inventory WordPress sites for Recover Exit For WooCommerce and identify installed versions.
- Disable or remove affected versions until vendor guidance confirms a fixed release.
- Monitor CVE, Wordfence, and WordPress plugin sources for remediation guidance.
- Reduce server-side file exposure and PHP permissions where operationally practical.
- Review WAF coverage for generic local file inclusion and traversal patterns.
Validation and detection
- Confirm whether Recover Exit For WooCommerce is installed on each WordPress site.
- Verify installed versions are not 1.0.3 or earlier unless vendor guidance says otherwise.
- Review plugin source for `tpf` reaching an `include()` path in `recover_exit()`.
- Check web logs for suspicious unauthenticated POST activity against plugin endpoints.
- Confirm affected sites have the plugin disabled, removed, or vendor-remediated.
Public sources used
Based on public source material and reviewed before publication.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-98: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-9662 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H 2.2 5.9 Wordfence Vulnerability scoring details
Base CVSS 3.1 score
8.1 HighVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reserved CVE Program
The CVE ID was reserved by the assigning CNA.
- Source timeline Wordfence
Disclosed
- CVE published CVE Program
The CVE record was published.
- CVE updated CVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 source CVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/10552714-c8fb-455c-ad61-c0ef2db4b69f?source=cve CVE reference, Wordfence
- https://plugins.trac.wordpress.org/browser/recoverexit-for-woocommerce/trunk/recover_exit_main.php#L42 CVE reference, Wordfence
- https://plugins.trac.wordpress.org/browser/recoverexit-for-woocommerce/tags/1.0.3/recover_exit_main.php#L42 CVE reference, Wordfence
- https://plugins.trac.wordpress.org/browser/recoverexit-for-woocommerce/trunk/recoverexit_woocommerce.php#L52 CVE reference, Wordfence
- https://plugins.trac.wordpress.org/browser/recoverexit-for-woocommerce/tags/1.0.3/recoverexit_woocommerce.php#L52 CVE reference, Wordfence
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.