# CVE-2025-2636: InstaWP Connect <= 0.1.0.85 - Unauthenticated Local PHP File Inclusion

> Unauthenticated attackers can include arbitrary local PHP files via a parameter, potentially leading to code execution or data disclosure.

- **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:** 11 Apr 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-422m-cg6f-h759

## What is CVE-2025-2636?

CVE-2025-2636 is a high-severity path traversal vulnerability in InstaWP Connect – 1-click WP Staging & Migration, published on 11 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

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

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2025-2636?


## How do I fix CVE-2025-2636?

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

## Is CVE-2025-2636 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-2636 exists.

Public exploit code:

- InstaWP Connect < 0.1.0.86 - Local PHP File Inclusion (nuclei): http/cves/2025/CVE-2025-2636.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-2636 and fix it if it is affected.

What it is: CVE-2025-2636 is a high-severity path traversal vulnerability in InstaWP Connect – 1-click WP Staging & Migration, published on 11 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-2636 exists.

Affected product: InstaWP Connect – 1-click WP Staging & Migration. 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-2025-2636/ (Markdown: https://insights.sbomify.com/CVE-2025-2636/index.md)
```

## Sources

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

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