dbcve.org
Wp All ExportWordPress extension · Soflyy

CVE-2024-7419

HIGH · 8.8 CVSS v3.1 Published 2025-02-07
Fix available
A fix is available. Upgrade to 1.9.2 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 Export Pro plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1.9.1 via the custom export fields. This is due to the missing input validation and sanitization of user-supplied data. This makes it possible for unauthenticated attackers to inject arbitrary PHP code into form fields that get executed on the server during the export, potentially leading to a complete site compromise. As a prerequisite, the custom export field should include fields containing user-supplied data.

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 Export Pro WordPress plugin versions up to 1.9.1 fail to validate and sanitize user-supplied data in custom export fields, allowing unauthenticated attackers to inject arbitrary PHP code that gets executed on the server during the export process, resulting in full site compromise.

MitigationUpdate the plugin to version 1.9.2 or later. If immediate patching is not possible, disable custom export field functionality or restrict exports to authenticated administrators only until the patch can be applied.

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 ExportWordPress extension
Affected:< 1.9.2

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Identify if WP ALL Export plugin is installed
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'WP All Export Pro' or 'WP All Export' in the list of active plugins.
    Affected if The plugin is present in the WordPress installation
  2. Check the installed version number
    In the Plugins list, locate WP All Export Pro and note the version number displayed below the plugin name. Alternatively, check the plugin file /wp-content/plugins/wp-all-export-pro/readme.txt or the main plugin PHP file for the 'Version' header.
    Affected if The version is below 1.9.2 (any version up to and including 1.9.1)
  3. Determine if custom export fields are in use
    Navigate to All Export > New Export. In the export configuration screen, check if the "Custom XML" or "Custom CSV" field type is being used, or if any fields under "Custom Field" or "PHP function" options are configured.
    Affected if Custom export fields or PHP functions are configured in any export template
  4. Verify export accessibility settings
    Check the export configuration to confirm whether the export functionality permits access by unauthenticated users. Look for settings under Export Settings that control who can run exports.
    Affected if Unauthenticated/external access to export functionality is allowed

You are affected if WP All Export Pro is installed with a version below 1.9.2 AND custom export fields or unauthenticated export access are enabled.

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

Update the plugin to version 1.9.2 or later. If immediate patching is not possible, disable custom export field functionality or restrict exports to authenticated administrators only until the patch can be applied.

Recommended fix High confidence

WP All Export version 1.9.2

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'WP All Export' (or 'WP All Export Pro') in the plugin list
  4. If an update is available, click 'Update Now' to update to version 1.9.2
  5. Alternatively, navigate to Plugins > Add New > Upload Plugin and upload the version 1.9.2 of the plugin package
  6. After updating, verify the current version is 1.9.2 or higher via the Plugins page

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

Fix this in Wp All Export Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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