CVE-2023-6750

WP Clone <= 2.4.2 - Sensitive Information Exposure

2023-12-18 00:00
Dmitrii Ignatyev

Strategic Overview

Status
Patched in 2.4.3
Affected Plugin
Clone
Affected Version
<= 2.4.2
CVSS
9.8Critical
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2023-6750
View all Clone vulnerabilities

At a glance

CVE-2023-6750 is a critical-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Clone WordPress plugin, affecting versions <= 2.4.2. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.4.3; sites on affected versions should update now. Disclosed December 2023, reported by Dmitrii Ignatyev.

Vulnerability Overview

The Clone plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.4.2. This makes it possible for unauthenticated attackers to download database backups made with the plugin resulting in the potential of a complete site takeover.

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 privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

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

Reaching this weakness in Clone <= 2.4.2 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 Clone the fix is 2.4.3: builds <= 2.4.2 are affected, anything from 2.4.3 onward is not.

Remediation

Update to version 2.4.3, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: Clone 2.4.3 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