InstaWP Connect <= 0.1.0.8 - Cross-Site Request Forgery via create_file_db_manager

2024-01-12 00:00
Anonymous

Strategic Overview

Status
Patched in 0.1.0.9
Affected Plugin
InstaWP Connect – 1-click WP Staging & Migration
Affected Version
<= 0.1.0.8
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE pending
View all InstaWP Connect – 1-click WP Staging & Migration vulnerabilities

At a glance

This record tracks a medium-severity Missing Authorization vulnerability in the InstaWP Connect WordPress plugin, affecting versions <= 0.1.0.8. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The issue is fixed in version 0.1.0.9; sites on affected versions should update now. Disclosed January 2024.

Vulnerability Overview

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.8. This is due to missing or incorrect nonce validation on the create_file_db_manager() function. This makes it possible for unauthenticated attackers to make use of the file and database manager functionality provided by the plugin via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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.

CWE-862: Missing Authorization

InstaWP Connect <= 0.1.0.8 carries this weakness at create_file_db_manager(), and reaching it takes a caller who can reach the endpoint. 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

https://www.wordfence.com/threat-intel/vulnerabilities/id/5954c35a-7d0a-4bc5-9cad-3223e7be56eb

Related records

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