Skip to content
Fencer Vulns
high 8.1

CVE-2025-2636 in the critical feed json

InstaWP Connect <= 0.1.0.85 - Unauthenticated Local PHP File Inclusion

published 2025-04-11 18 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-10733

cvss
8.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
10.6%
EPSS 10.6% chance of exploitation in 30 days, percentile 95%
public exploits
0
none known, plus a Nuclei check

Summary

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.

Patch / fix

  • instawp instawp_connect 0.1.0.86

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
18 mo ago

Exploit prediction

10.60% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • Nuclei template InstaWP Connect < 0.1.0.86 - Local PHP File Inclusion nuclei detection template

CVSS scores

assigned by version score vector
CNA 3.1 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

  • instawp InstaWP Connect – 1-click WP Staging & Migration

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.