dbcve.org
Backup And MigrationWordPress extension · Webtoffee

CVE-2024-31254

HIGH · 7.5 CVSS v3.1 Published 2024-04-10
Fix available
A fix is available. Upgrade to 1.4.8 or later.
See remediation →
84/100
Remediation priority · High
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.This issue affects WordPress Backup & Migration: from n/a through 1.4.7.

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 WordPress Backup & Migration plugin by WebToffee versions up to 1.4.7 contains a vulnerability where sensitive information is being written to log files. This could allow unauthorized users with access to log files to obtain credentials, session tokens, or other sensitive data that the backup/migration tool processes.

MitigationUpdate the WebToffee WordPress Backup & Migration plugin to the latest patched version as soon as available. Additionally, restrict access to log directories and ensure proper file permissions are in place.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Backup And MigrationWordPress extension
Affected:< 1.4.8

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/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. Verify the WebToffee Backup & Migration plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate 'WebToffee Backup And Migration' or 'Webtoffee Backup And Migration' in the list. Note the version number displayed below the plugin name.
    Affected if The plugin is installed and the displayed version is less than 1.4.8 (for example, 1.4.7, 1.4.6, etc.)
  2. Check the plugin version via WP-CLI if available
    Run the command 'wp plugin list --plugin=wt-backup-migration' or 'wp plugin list' and filter for the backup/migration plugin to confirm the exact installed version.
    Affected if The command output shows a version number below 1.4.8
  3. Locate plugin log files in the WordPress installation
    Search common log directories within the plugin folder (typically /wp-content/plugins/wt-backup-migration/ or similar) and the /wp-content/ directory for files with .log extensions that may have been created by the backup plugin. Check /wp-content/uploads/ and /wp-content/ as well if logging is enabled.
    Affected if Log files exist in the plugin directory or related WordPress directories and contain sensitive data such as passwords, API keys, or session tokens in plain text
  4. Inspect plugin settings for logging configuration
    Access the plugin settings page in WordPress admin (usually under the plugin menu) and look for options related to logging, debug logs, or log file generation. Determine if logging is currently enabled or was enabled previously.
    Affected if Logging or debug features are or were enabled in the plugin settings

You are affected if the WebToffee Backup & Migration plugin is installed with a version lower than 1.4.8 AND log files exist in your environment that may contain exposed sensitive data.

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
Upgrade available Upgrade to 1.4.8 or later
Fixed in 1.4.8
Interim mitigation

Update the WebToffee WordPress Backup & Migration plugin to the latest patched version as soon as available. Additionally, restrict access to log directories and ensure proper file permissions are in place.

Recommended fix High confidence

1.4.8

  1. Backup your WordPress site and database before making any changes
  2. Log in to your WordPress admin dashboard
  3. Navigate to Plugins > Installed Plugins
  4. Locate the 'Backup And Migration' plugin by WebToffee
  5. Check the current version installed - if it is below 1.4.8, an update is required
  6. Click 'Update now' or 'Update' to install version 1.4.8 or later
  7. Verify the plugin updated successfully by confirming the version number
  8. Review any new plugin settings or changelog for recommended configurations

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

Fix this in Backup And Migration Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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