dbcve.org
Sensitive Information in LogsWeakness · CWE-532

CVE-2025-24651

MEDIUM · 5.9 CVSS v3.1 Published 2025-04-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/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 WebToffee WordPress Backup & Migration wp-migration-duplicator allows Retrieve Embedded Sensitive Data.This issue affects WordPress Backup & Migration: from n/a through <= 1.5.3.

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 WebToffee WordPress Backup & Migration plugin (wp-migration-duplicator) versions up to 1.5.3 contains a vulnerability where sensitive information is being written to log files, allowing authenticated or external attackers to retrieve this embedded sensitive data from the log files.

MitigationUpdate the WebToffee WordPress Backup & Migration plugin to the latest version which should contain a fix for this issue. Additionally, review and secure any existing log files that may contain sensitive data, and ensure log files are stored outside publicly accessible directories.

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/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 plugin installation
    Check if the WebToffee WordPress Backup & Migration plugin (wp-migration-duplicator) is installed on the WordPress site. This can be done via WordPress admin dashboard under Plugins, or by checking the /wp-content/plugins/ directory for the wt-migration-duplicator folder.
    Affected if The plugin is installed and active on the WordPress site.
  2. Check installed version number
    Locate the plugin version in the WordPress admin under Plugins > Installed Plugins, or read the main plugin file (usually wt-migration-duplicator.php) and look for the 'Version' header in the file comments.
    Affected if The installed version is 1.5.3 or any earlier version (versions up to and including 1.5.3 are affected).
  3. Locate plugin log directories
    Check the following typical locations for log files: /wp-content/uploads/wt-migration/logs/, /wp-content/plugins/wt-migration-duplicator/logs/, or any custom log path configured in plugin settings. Use file system access or a file manager to list these directories.
    Affected if Log directories or log files exist on the server.
  4. Verify log file accessibility
    Check if the identified log files are stored in web-accessible directories (within /wp-content/ or /wp-content/uploads/). Try accessing a known log file via a web browser request to see if it is publicly downloadable.
    Affected if Log files are stored in publicly accessible web directories and can be accessed via HTTP requests.
  5. Inspect log contents for sensitive data
    Open the log files using a text editor or command line (cat, less, head). Search for patterns that may indicate sensitive information such as: database credentials, password strings, API keys, or authentication tokens.
    Affected if Log files contain plaintext sensitive information such as passwords, database credentials, or API keys.

The environment is affected if the WebToffee WordPress Backup & Migration plugin is installed with version 1.5.3 or earlier AND log files containing sensitive data exist in web-accessible directories.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the WebToffee WordPress Backup & Migration plugin to the latest version which should contain a fix for this issue. Additionally, review and secure any existing log files that may contain sensitive data, and ensure log files are stored outside publicly accessible directories.

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-2025-24651 — 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-2025-24651 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