CVE-2023-3132

MainWP Child <= 4.4.1.1 - Information Disclosure via Back-Up Files

2023-06-23 00:00
Robert Lockwood

Strategic Overview

Status
Patched in 4.4.1.2
Affected Version
<= 4.4.1.1
CVSS
5.9Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2023-3132
View all MainWP Child – Securely Connects to the MainWP Dashboard to Manage Multiple Sites vulnerabilities

At a glance

CVE-2023-3132 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the MainWP Child WordPress plugin, affecting versions <= 4.4.1.1. It carries a CVSS score of 5.9 (reachable over the network; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 4.4.1.2; sites on affected versions should update now. Disclosed June 2023, reported by Robert Lockwood.

Vulnerability Overview

The MainWP Child plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 4.4.1.1 due to insufficient controls on the storage of back-up files. This makes it possible for unauthenticated attackers to extract sensitive data including the entire installations database if a backup occurs and the deletion of the back-up files fail.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in MainWP Child <= 4.4.1.1 takes a caller who can reach the endpoint. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For MainWP Child the fix is 4.4.1.2: builds <= 4.4.1.1 are affected, anything from 4.4.1.2 onward is not.

Remediation

Update to version 4.4.1.2, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: MainWP Child 4.4.1.2 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

Related records

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