dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2024-9624

HIGH · 7.6 CVSS v3.1 Published 2024-12-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/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 Server-Side Request Forgery in all versions up to, and including, 4.9.3 due to missing SSRF protection on the pmxi_curl_download function. This makes it possible for authenticated attackers, with Administrator-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services. On cloud platforms, it might allow attackers to read the Instance metadata.

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.3 contain an SSRF vulnerability in the pmxi_curl_download function due to missing protection on server-side requests. Authenticated administrators can abuse this to make arbitrary web requests from the server, potentially accessing internal services or cloud instance metadata.

MitigationUpdate to WP All Import Pro version 4.9.4 or later which includes SSRF protection. If immediate updating is not feasible, restrict administrator-level access and implement network-level controls to monitor for suspicious outbound requests.

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:L/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 WP All Import Pro is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP All Import Pro' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'wp-all-import-pro' or similar.
    Affected if The plugin is present on the WordPress site
  2. Check the installed version number
    In WordPress admin, go to Plugins > Installed Plugins and find WP All Import Pro. The version number is displayed below the plugin name. Compare it to the affected range: versions up to and including 4.9.3 are vulnerable.
    Affected if The installed version is 4.9.3 or lower
  3. Confirm administrator-level access exists
    Review WordPress user roles on your site. Check if any user accounts have the Administrator role, as the vulnerability requires an authenticated administrator to exploit.
    Affected if There are one or more user accounts with Administrator role who can access the plugin
  4. Check if pmxi_curl_download function is accessible
    The vulnerability exists in the pmxi_curl_download function which handles file downloads for imports. This function is part of the plugin's import functionality. If the plugin allows URL-based imports (using a remote file URL as the import source), the vulnerable code path is exposed.
    Affected if The plugin is configured to allow imports from remote URLs, making the pmxi_curl_download function reachable

You are affected if WP All Import Pro is installed, the version is 4.9.3 or lower, an administrator account exists on the site, and remote URL imports are enabled, allowing the pmxi_curl_download function to be exploited for SSRF.

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 to WP All Import Pro version 4.9.4 or later which includes SSRF protection. If immediate updating is not feasible, restrict administrator-level access and implement network-level controls to monitor for suspicious outbound requests.

Recommended fix Moderate confidence

Latest version of WP All Import Pro (version > 4.9.3)

  1. Check the current version of WP All Import Pro plugin installed on the WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate WP All Import Pro and note the current version number
  4. Update the plugin to the latest available version from the official WordPress plugin repository or from WP All Import's website
  5. After updating, verify the plugin version has been incremented beyond 4.9.3
  6. Ensure the site is functioning normally after the update

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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