dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-9162

HIGH · 7.2 CVSS v3.1 Published 2024-10-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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
The All-in-One WP Migration and Backup plugin for WordPress is vulnerable to arbitrary PHP Code Injection due to missing file type validation during the export in all versions up to, and including, 7.86. This makes it possible for authenticated attackers, with Administrator-level access and above, to create an export file with the .php extension on the affected site's server, adding an arbitrary PHP code to it, which may make remote code execution possible.

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 All-in-One WP Migration and Backup plugin for WordPress fails to validate file types during the export process, allowing authenticated administrators to create export files with .php extensions containing arbitrary PHP code. This enables potential remote code execution on the affected WordPress installation.

MitigationUpdate the plugin to version 7.87 or later which contains proper file type validation; if immediate update is not possible, restrict Administrator-level access to export functionality and monitor for suspicious .php files in export 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
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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. Confirm the plugin is installed
    Navigate to WordPress admin dashboard > Plugins and look for 'All-in-One WP Migration and Backup' in the installed plugins list
    Affected if The plugin is not installed on the WordPress site
  2. Check the installed version
    In the Plugins list, locate the All-in-One WP Migration entry and note the version number displayed beneath the plugin name
    Affected if The installed version is lower than the version that contains proper file type validation (i.e., the plugin is outdated)
  3. Verify Administrator role access to export
    Navigate to the All-in-One WP Migration settings or export page while logged in as an Administrator; confirm the export functionality is accessible
    Affected if Administrator-level accounts can access and use the export feature without additional restrictions
  4. Inspect export output directory
    Locate the default export directory (typically /wp-content/ai1wm-backups/ or as configured in plugin settings); list all files and note their extensions
    Affected if Any .php files are present in the export directory, especially those not expected from normal operation
  5. Review recent export file types
    Check the export history or directory for files created by the plugin; note file extensions of recent exports
    Affected if Recent exports have .php extensions instead of the standard .wpress or archive format

The environment is affected if the All-in-One WP Migration and Backup plugin is installed, the version lacks proper file type validation, and the export feature produces or permits .php files in export 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 7.87 or later which contains proper file type validation; if immediate update is not possible, restrict Administrator-level access to export functionality and monitor for suspicious .php files in export directories.

Recommended fix High confidence

All-in-One WP Migration and Backup version 7.87 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'All-in-One WP Migration and Backup' plugin
  4. Click 'Update Now' to install the latest version, or manually update to version 7.87 or higher if automatic update is not available
  5. Verify the update was successful by checking the plugin version

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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