The InstaWP Connect – 1-click WP Staging & Migration plugin for WordPress is vulnerable to arbitrary file uploads due to insufficient file validation in the /wp-json/instawp-connect/v1/config REST API endpoint in all versions up to, and including, 0.1.0.22. This makes it possible for unauthenticated attackers to upload arbitrary files.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a Python proof-of-concept exploit (CVE-2024-2667.py) targeting a vulnerability in the InstaWP Connect WordPress plugin (versions 0.1.0.22 and below). The exploit leverages insufficient file validation in the /wp-json/instawp-connect/v1/config REST API endpoint, allowing unauthenticated attackers to upload arbitrary files (such as a PHP web shell) to the target site. The script first checks the plugin version by fetching the readme.txt file, then attempts the file upload using a crafted POST request. If successful, the uploaded shell is typically accessible at wp-content/plugins/instawp-connect/shell.php. The repository also includes a README.md with detailed usage instructions and vulnerability information. The exploit is a standalone Python script and does not rely on any exploitation framework.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.