CVE-2025-2636: InstaWP Connect (WordPress plugin) · Path Traversal
Affects InstaWP Connect (WordPress plugin)Source CVE Database V5
Not known to be exploited · public detection template (Nuclei) · 10% EPSS · CVSS 8.1 High.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 10.5% chance of exploitation in 30 days – higher than 95% 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 11 Apr 2025
Detectable: evidence found.
nuclei template: InstaWP Connect < 0.1.0.86 - Local PHP File Inclusion
Weaponised: 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 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| instawp InstaWP Connect – 1-click WP Staging & Migration | Affected
| Fixed in– |
AI-suggested
Mitigation may require restricting access to the vulnerable parameter or disabling the plugin until a fix is released. No generic mitigations are recommended beyond this due to the specific nature of the vulnerability.
Description
The InstaWP Connect – 1-click WP Staging & Migration plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 0.1.0.85 via the 'instawp-database-manager' parameter. This makes it possible for unauthenticated attackers to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where php file types can be uploaded and included, or are already present on the filesystem locally. There are currently no known vulnerabilities in this plugin that make file upload possible, meaning this won't be exploitable to achieve remote code execution on most instances with just this plugin alone. Another vulnerability would need to be present on the site allowing arbitrary file upload in order to leverage this to achieve remote code execution.