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

Medium 5.3 Published Updated

Unauthenticated attackers can extract sensitive system data and license keys from log files if specific admin settings are enabled.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2024-3682?

CVE-2024-3682 is a medium-severity vulnerability in WPStaging WP STAGING Pro WordPress Backup Plugin, published on 26 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

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.

Weakness: CWE-200

Which versions are affected by CVE-2024-3682?

How do I fix CVE-2024-3682?

No fix has been published for CVE-2024-3682 yet. Limit exposure of the affected software until one is available.

Is CVE-2024-3682 being exploited?

There is no known exploitation of CVE-2024-3682 in the wild and no public exploit code.

Sources

Also known as GHSA-q66w-qfxv-vpx3.

Is CVE-2024-3682 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free