CVE-2024-25918

InstaWP Connect <= 0.1.0.8 - Authenticated (Subscriber+) Remote Code Execution

2024-02-14 00:00
Majed Refaea

Strategic Overview

Status
Patched in 0.1.0.9
Affected Version
<= 0.1.0.8
CVSS
8.8High
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-25918
View all InstaWP Connect – 1-click WP Staging & Migration vulnerabilities

At a glance

CVE-2024-25918 is a high-severity Missing Authorization vulnerability in the InstaWP Connect WordPress plugin, affecting versions <= 0.1.0.8. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 0.1.0.9; sites on affected versions should update now. Disclosed February 2024, reported by Majed Refaea.

Vulnerability Overview

The InstaWP Connect – 1-click WP Staging & Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 0.1.0.8. This makes it possible for authenticated attackers, with subscriber-level access and above, to execute code on the server.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-862: Missing Authorization

Reaching this weakness in InstaWP Connect <= 0.1.0.8 takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For InstaWP Connect the fix is 0.1.0.9: builds <= 0.1.0.8 are affected, anything from 0.1.0.9 onward is not.

Remediation

Update to version 0.1.0.9, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: InstaWP Connect 0.1.0.9 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C