CVE-2024-13913 HIGH

CVE-2024-13913: InstaWP Connect – 1-click WP Staging & Migration <= 0.1.0.83 - Cross-Site Request Forgery to Local File Inclusion

Vendor Instawp
Product InstaWP Connect – 1-click WP Staging & Migration
Weakness CWE-352 · CSRF
Published March 14, 2025
Last update April 8, 2026

CVSS base score

8.8/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction Required
Confidentiality High
Integrity High

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

What the vulnerability does

01Description

The InstaWP Connect – 1-click WP Staging & Migration plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 0.1.0.83. This is due to missing or incorrect nonce validation in the '/migrate/templates/main.php' file. 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 images and other “safe” file types can be uploaded and included.

Explanation of Vulnerability in Simple Terms

02Summary

InstaWP Connect versions up to 0.1.0.83 are vulnerable to cross-site request forgery (CSRF) attacks. An attacker can trick a logged-in site administrator into visiting a malicious webpage that performs unauthorized actions on the site, such as modifying settings or creating accounts. The vulnerability requires the victim to click a link or visit a page, but no special privileges are needed on the attacker's side.

What an attacker can do

03Attacker Capabilities

Trick a logged-in admin into performing unauthorized actions like changing settings or creating accounts via a malicious webpage.

Potential impact on your site

04Site Impact

An attacker can modify your site settings, create unauthorized accounts, or perform other admin actions without your knowledge.

Conditions required to exploit

05Prerequisites

Victim must be logged into WordPress and visit an attacker-controlled page or click a malicious link.

Key dates

06Disclosure timeline

March 14, 2025 CVE published
April 8, 2026 Record updated