CloneWordPress extension · Backupbliss

CVE-2024-43298

HIGH · 8.8 CVSS v3.1 Published 2024-11-01
Fix available
A fix is available. Upgrade to 2.4.6 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Missing Authorization vulnerability in Migrate Clone allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Clone: from n/a through 2.4.5.

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

This is a missing authorization vulnerability in the Migrate Clone plugin (likely a WordPress migration/duplication plugin). The flaw allows attackers to exploit incorrectly configured access control security levels, potentially bypassing authorization checks to perform actions they should not have permission to perform.

MitigationUpdate to the latest version of Migrate Clone (beyond 2.4.5) when available, and conduct a thorough code review to identify and remediate all locations where authorization checks are missing or improperly implemented.

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
CloneWordPress extension
Affected:< 2.4.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 Backupbliss Clone plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Backupbliss Clone' or 'Migrate Clone' in the list of active plugins
    Affected if The plugin appears in the installed plugins list and is activated
  2. Check installed plugin version
    Click on the plugin name in the WordPress plugins list to view its details, or inspect the plugin header in wp-content/plugins/backupbliss-clone/backupbliss-clone.php for the 'Version' field
    Affected if The version number displayed is lower than 2.4.6 (e.g., 2.4.5, 2.4.4, etc.)
  3. Confirm plugin is accessible to untrusted users
    Review WordPress user roles and capabilities. Check if any user role other than Administrator has access to the plugin's admin menu or if the plugin exposes any public-facing endpoints (check for rewrite rules or AJAX actions starting with 'backupbliss_' or 'migrate_clone_')
    Affected if Non-administrator users have access to the plugin functionality or the plugin registers publicly accessible AJAX or REST endpoints without capability checks

You are affected if Backupbliss Clone or Migrate Clone plugin is installed with a version lower than 2.4.6 and the plugin or its features are accessible to users without administrator privileges.

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 2.4.6 or later
Fixed in 2.4.6
Interim mitigation

Update to the latest version of Migrate Clone (beyond 2.4.5) when available, and conduct a thorough code review to identify and remediate all locations where authorization checks are missing or improperly implemented.

Recommended fix Moderate confidence

Upgrade to Migrate Clone version 2.4.6

  1. 1. Create a full backup of your WordPress site (database and files) before updating.
  2. 2. Navigate to WordPress Admin Dashboard > Plugins > Installed Plugins.
  3. 3. Locate the 'Migrate Clone' plugin in the list.
  4. 4. If an update is available, click 'Update Now' to update to version 2.4.6.
  5. 5. Alternatively, navigate to Dashboard > Updates and apply available updates.
  6. 6. Verify the plugin version is now 2.4.6 by checking the plugins list.
  7. 7. Test the plugin functionality to ensure it works correctly after the update.

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

Fix this in Clone Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,670
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-43298 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