dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2024-30225

CRITICAL · 10.0 CVSS v3.1 Published 2024-03-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Deserialization of Untrusted Data vulnerability in WPENGINE, INC. WP Migrate.This issue affects WP Migrate: from n/a through 2.6.10.

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

A Deserialization of Untrusted Data vulnerability in the WP Migrate WordPress plugin allows attackers to potentially execute arbitrary code by exploiting unsafe deserialization of data. The CVSS 10 score indicates this is a remotely exploitable, low-complexity attack requiring no authentication that leads to complete system compromise.

MitigationUpdate WP Migrate to the latest patched version immediately. If no patched version is available, disable the plugin until a fix is released.

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 WP Migrate plugin is installed
    Check the WordPress plugin directory (wp-content/plugins/) or view installed plugins in WordPress admin under Plugins > Installed Plugins
    Affected if WP Migrate plugin files exist in the plugins directory
  2. Determine installed WP Migrate version
    Open the main plugin file (wp-content/plugins/wp-migrate/wp-migrate.php) and locate the version comment in the file header, or check the version displayed in WordPress admin plugins list
    Affected if The version number cannot be determined or is older than the patched release
  3. Confirm plugin is active
    In WordPress admin, check if WP Migrate shows as 'Active' under Plugins > Installed Plugins, or query the wp_options table for option_name='active_plugins'
    Affected if Plugin is activated and accessible to unauthenticated users
  4. Check for exposed migration import functionality
    Inspect if the plugin's import/backup restore feature is publicly accessible. Look for AJAX actions or endpoints related to 'import', 'restore', or 'migrate' in the plugin's admin-ajax.php calls or API routes
    Affected if Deserialization endpoints accept unauthenticated input without validation
  5. Review plugin data handling configuration
    Examine the plugin settings under WP Migrate > Settings for any options that enable data import, restore, or migration pulling from external sources
    Affected if Import/restore features are enabled and process serialized data from user-controlled sources

If WP Migrate is installed, active, and processes unvalidated serialized data through accessible import or migration features, the environment is likely affected by this deserialization vulnerability

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 Migrate to the latest patched version immediately. If no patched version is available, disable the plugin until a fix is released.

Recommended fix Moderate confidence

Version higher than 2.6.10 (check WordPress Plugin Repository for latest version)

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard.
  3. 3. Locate WP Migrate in the plugin list.
  4. 4. If an update is available, click 'Update Now' to install the latest version.
  5. 5. Alternatively, you can manually download the latest version from the WordPress Plugin Repository and upload it via Plugins > Add New > Upload Plugin.
  6. 6. Verify the update was successful by checking the plugin version number.
  7. 7. Test that WP Migrate functionality works as expected after the update.
Caveat Review plugin changelog for any breaking changes between your current version and the new version

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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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