CVE-2024-3682

WP STAGING <= 3.4.3 and WP STAGING Pro <= 5.4.3 - Sensitive Information Exposure via Log File

2024-04-25 00:00
haidv35

Strategic Overview

Status
Patched in 5.5.0
Affected Version
<= 5.4.3
CVSS
5.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2024-3682
View all WP STAGING Pro WordPress Backup Plugin vulnerabilities

At a glance

CVE-2024-3682 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the WP STAGING Pro WordPress Backup Plugin WordPress plugin, affecting versions <= 5.4.3. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 5.5.0; sites on affected versions should update now. Disclosed April 2024, reported by haidv35.

Vulnerability Overview

The WP STAGING and WP STAGING Pro plugins for WordPress are vulnerable to Sensitive Information Exposure in versions up to, and including, 3.4.3, and versions up to, and including, 5.4.3, respectively, via the ajaxSendReport function. This makes it possible for unauthenticated attackers to extract sensitive data from a log file, including system information and (in the Pro version) license keys. Successful exploitation requires an administrator to have used the 'Contact Us' functionality along with the "Enable this option to automatically submit the log files." option.

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.

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

Reaching this weakness in WP STAGING Pro WordPress Backup Plugin <= 5.4.3 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 WP STAGING Pro WordPress Backup Plugin the fix is 5.5.0: builds <= 5.4.3 are affected, anything from 5.5.0 onward is not.

Remediation

Update to version 5.5.0, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: WP STAGING Pro WordPress Backup Plugin 5.5.0 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