dbcve.org
Wp All ImportWordPress extension · Soflyy

CVE-2024-9664

HIGH · 7.2 CVSS v3.1 Published 2025-02-07
Fix available
A fix is available. Upgrade to 4.9.8 or later.
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 WP All Import Pro plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 4.9.7 via deserialization of untrusted input from an import file. This makes it possible for authenticated attackers, with Administrator-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable software. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code.

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 WP All Import Pro plugin for WordPress versions up to 4.9.7 is vulnerable to PHP Object Injection through unsafe deserialization of untrusted data in import files. Authenticated administrators can inject PHP objects via crafted import files; while no POP chain exists in the plugin itself, one present in other installed plugins/themes could enable arbitrary file deletion, data theft, or code execution.

MitigationUpgrade to version 4.9.8 or later, which implements secure deserialization or input validation. Until then, restrict administrator-level access strictly and audit installed plugins/themes for potential POP chains.

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
Wp All ImportWordPress extension
Affected:< 4.9.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
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. Verify WP All Import Pro is installed
    Locate the plugin in your WordPress installation under wp-content/plugins/ or use the WordPress plugins admin page to confirm WP All Import or WP All Import Pro is active
    Affected if The plugin is present and active in the WordPress installation
  2. Determine installed plugin version
    Check the plugin header in wp-all-import-pro.php or view the installed version number displayed in the WordPress plugins admin page under the plugin name
    Affected if The installed version is less than 4.9.8 (for example, 4.9.7, 4.9.6, etc.)
  3. Confirm administrator access exists
    Review WordPress user roles to verify that administrator accounts exist and can access the WP All Import functionality via the admin dashboard
    Affected if Administrator role users are present and can access the plugin's import features
  4. Check for import file upload capability
    Navigate to the WP All Import section in the admin panel and confirm that import templates or XML/CSV files can be created or uploaded by administrators
    Affected if Administrators can create or upload import files without additional security restrictions

You are affected if WP All Import Pro is installed with a version lower than 4.9.8 and administrator-level users have access to create or upload import files.

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

Upgrade to version 4.9.8 or later, which implements secure deserialization or input validation. Until then, restrict administrator-level access strictly and audit installed plugins/themes for potential POP chains.

Recommended fix High confidence

WP All Import Pro 4.9.8

  1. Backup your WordPress site and database before making any changes
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Find WP All Import Pro in the plugin list
  4. Click 'Update now' if an update is available, or manually upload version 4.9.8
  5. Verify the plugin was updated to version 4.9.8 or later
  6. Test that imports still function correctly in a staging environment if possible
Caveat No breaking changes documented; always test updates in staging first

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

Fix this in Wp All Import Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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