dbcve.org
Sensitive Information in LogsWeakness · CWE-532

CVE-2024-33922

MEDIUM · 5.3 CVSS v3.1 Published 2024-05-02
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
Insertion of Sensitive Information into Log File vulnerability in Jordy Meow WP Media Cleaner.This issue affects WP Media Cleaner: from n/a through 6.7.2.

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 Media Cleaner plugin for WordPress versions up to 6.7.2 contains an insertion of sensitive information into log file vulnerability. The plugin writes sensitive data (potentially including authentication credentials, session tokens, or user-specific information) directly to log files without proper sanitization or redaction. This could expose confidential data to anyone with access to the server's log files.

MitigationUpdate WP Media Cleaner to the latest version when available, or implement server-side log access controls and ensure log files are stored with restricted permissions. Review existing logs for any exposed sensitive data.

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. Verify WP Media Cleaner plugin is installed
    Access WordPress admin dashboard and navigate to Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for the wp-media-cleaner folder
    Affected if The WP Media Cleaner plugin is present in the WordPress installation
  2. Check installed plugin version
    In WordPress admin, view the plugin details to see the version number, or read the main plugin PHP file header for the 'Version' field
    Affected if The installed version is 6.7.2 or any earlier version (versions up to and including 6.7.2 are affected)
  3. Confirm plugin logging is active
    Check plugin settings page in WordPress admin under WP Media Cleaner options, or inspect the plugin configuration stored in wp_options database table for wpmc_* entries
    Affected if Logging or debug mode is enabled in the plugin settings
  4. Locate potential log files
    Check common WordPress log directories: /wp-content/debug.log, /wp-content/wpmc-debug.log, or custom log paths configured in wp-config.php (WP_DEBUG_LOG constant)
    Affected if Log files exist in the WordPress environment
  5. Inspect log contents for sensitive data
    Read log files using cat, less, or a text editor. Search for patterns indicating sensitive information: password=, 'password', api_key, session, Authorization headers, or database credentials
    Affected if Log files contain unredacted sensitive data such as authentication credentials, session tokens, or user-specific information written by the plugin

A user is affected if WP Media Cleaner version 6.7.2 or earlier is installed AND logging is enabled, resulting in sensitive data being written to log files accessible on the server.

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 Media Cleaner to the latest version when available, or implement server-side log access controls and ensure log files are stored with restricted permissions. Review existing logs for any exposed sensitive data.

Recommended fix Moderate confidence

Latest version after 6.7.2 (check WordPress plugin repository for current release)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate WP Media Cleaner
  4. 4. Check if an update is available and install the latest version
  5. 5. Alternatively, download the latest version from the official WordPress plugin repository or vendor website
  6. 6. Verify the plugin updated successfully

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-33922 — 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-33922 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