dbcve.org
Backup MigrationWordPress extension · Backupbliss

CVE-2023-6266

HIGH · 7.5 CVSS v3.1 Published 2024-01-11
Fix available
A fix is available. Upgrade to after 1.3.6 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
The Backup Migration plugin for WordPress is vulnerable to unauthorized access of data due to insufficient path and file validation on the BMI_BACKUP case of the handle_downloading function in all versions up to, and including, 1.3.6. This makes it possible for unauthenticated attackers to download back-up files which can contain sensitive information such as user passwords, PII, database credentials, and much more.

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 · high confidence

The Backup Migration WordPress plugin has an unauthenticated arbitrary file download vulnerability in the handle_downloading function's BMI_BACKUP case. The plugin fails to validate file paths properly, allowing attackers to request any accessible file on the server including backup archives containing sensitive data like user credentials, PII, and database credentials.

MitigationUpdate the Backup Migration plugin to version 1.3.7 or later which includes proper path and file validation. If immediate update is not possible, consider disabling the plugin or restricting access via web server configuration.

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 MigrationWordPress extension
Affected:<= 1.3.6

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 Backup Migration plugin is installed
    Check your WordPress plugins directory for the Backup Migration plugin (backup-migration) or check wp-content/plugins/ for a folder named 'backup-migration' or similar. In WordPress admin, go to Plugins > Installed Plugins and look for 'Backup Migration' or 'Backupbliss Backup Migration'.
    Affected if The plugin is present in the WordPress installation
  2. Identify the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and click on the Backup Migration plugin to view its details. The version number will be displayed in the plugin metadata. Alternatively, check the main plugin file header in wp-content/plugins/[plugin-folder]/backup-migration.php for the 'Version' tag.
    Affected if The version number is 1.3.6 or lower (any version <= 1.3.6)
  3. Confirm the vulnerable download endpoint exists
    Check if the plugin registers AJAX handlers or route handlers for file downloads. Examine the plugin files for the handle_downloading function and look for the 'BMI_BACKUP' case. The vulnerable endpoint typically responds to requests with action parameter related to downloading backups.
    Affected if The plugin code contains the handle_downloading function with a BMI_BACKUP case that lacks proper path validation
  4. Check if backup archives exist on the server
    Search the wp-content/uploads/backup-migration/ directory (or similar backup storage paths configured in the plugin) for .zip, .tar.gz, or other backup archive files. These files may contain sensitive database exports and configuration backups.
    Affected if Backup archives exist and could be downloaded via the vulnerable endpoint
  5. Test if the download endpoint is accessible without authentication
    If safe to do so in a non-production environment, attempt a request to the suspected download endpoint (commonly wp-admin/admin-ajax.php?action=bm_download or similar) without providing valid authentication credentials. The vulnerability allows unauthenticated access.
    Affected if The download endpoint responds to unauthenticated requests

Your environment is affected if the Backup Migration plugin version is 1.3.6 or lower and the vulnerable download handler is accessible, allowing unauthenticated attackers to download arbitrary files including backup archives.

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 a release after 1.3.6
Interim mitigation

Update the Backup Migration plugin to version 1.3.7 or later which includes proper path and file validation. If immediate update is not possible, consider disabling the plugin or restricting access via web server configuration.

Recommended fix High confidence

Backup Migration 1.3.7 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'Backup Migration' plugin
  4. Click 'Update now' if an update is available, or manually upload version 1.3.7 or later from the WordPress plugin repository
  5. Verify the update was successful by checking the plugin version

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

Fix this in Backup Migration Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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