dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-3682

MEDIUM · 5.3 CVSS v3.1 Published 2024-04-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The WP STAGING and WP STAGING Pro plugins contain an unauthenticated sensitive information exposure vulnerability in the ajaxSendReport function. When an administrator uses the 'Contact Us' functionality with the automatic log submission option enabled, sensitive data including system information (and license keys in the Pro version) is written to log files. The ajaxSendReport function does not properly restrict access, allowing unauthenticated attackers to read these log files via the vulnerable function.

MitigationUpdate WP STAGING and WP STAGING Pro to the latest patched versions. As a temporary measure, disable the 'automatically submit the log files' option in plugin settings. Consider rotating any exposed license keys or credentials found in log files.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm WP STAGING plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for WP STAGING or WP STAGING Pro. Note the installed version number displayed there.
    Affected if The plugin is installed and the version is unpatched (compare to vendor's security advisory for fixed version)
  2. Check if automatic log submission is enabled
    In WordPress admin, navigate to WP STAGING settings. Look for the 'Contact Us' or 'Support' section and check whether the option to 'automatically submit log files' or similar is enabled.
    Affected if The automatic log submission option is turned ON, as this is required for the vulnerable code path to write sensitive data to logs
  3. Locate log files created by the plugin
    Access the WordPress wp-content directory via FTP or file manager. Look for log files in common locations such as wp-content/uploads/wp-staging/logs/, wp-content/debug.log, or similar paths. Check for files with names containing 'log', 'staging', or 'debug'.
    Affected if Log files exist in the wp-content directory or subdirectories, as these may contain the exposed system information or license keys
  4. Inspect log file contents for sensitive data
    Open any found log files and search for sensitive patterns: system paths, PHP version info, database credentials references, license key strings (typically alphanumeric in Pro version), or WP STAGING configuration details.
    Affected if Log files contain system information, license keys, or other sensitive configuration data that should not be publicly accessible
  5. Verify unauthenticated access to ajaxSendReport
    Test by sending a direct POST request to your site's wp-admin/admin-ajax.php with action=wpstg_ajaxSendReport and observe if the server responds without requiring authentication.
    Affected if The ajaxSendReport function responds to unauthenticated requests, confirming the access control weakness exists

You are affected if WP STAGING with automatic log submission enabled is running an unpatched version and log files containing sensitive data are accessible to unauthenticated users via the ajaxSendReport function.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update WP STAGING and WP STAGING Pro to the latest patched versions. As a temporary measure, disable the 'automatically submit the log files' option in plugin settings. Consider rotating any exposed license keys or credentials found in log files.

Recommended fix Moderate confidence

WP STAGING free: 3.4.4+ | WP STAGING Pro: 5.4.4+

  1. Upgrade WP STAGING (free) plugin to version 3.4.4 or later
  2. Upgrade WP STAGING Pro plugin to version 5.4.4 or later

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-3682 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-3682 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data