CVE-2024-7419: The WP ALL Export Pro plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and i

Q: How do I fix CVE-2024-7419?

wp all export: upgrade to 1.9.2. Exact commands for each OS are on this page.

Q: Is CVE-2024-7419 being exploited?

CVE-2024-7419 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-7419 affect?

CVE-2024-7419 affects wp all export. Severity is high (CVSS 8.3). 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 month

HIGH 8.3UPGRADE

CVE-2024-7419 is a high-severity flaw (CVSS 8.3) affecting wp all export. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 pr

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.3 (High)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.6% (top 50%)
CISA exploited list	No
Weakness	CWE-94
Published	2025-02-07
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: soflyy

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-02-07 16:15 UTCPublished CVE record published
2026-06-17 08:20 UTCUpdated Record last modified

soflyy wp all export UPGRADE

Affected: < 1.9.2

Fixed in: 1.9.2

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy wp-all-export || rpm -q wp-all-export || wp-all-export --version

2. UPGRADE to 1.9.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade wp-all-export

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wp-all-export

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-7419?

wp all export: upgrade to 1.9.2. Exact commands for each OS are on this page.

Is CVE-2024-7419 being exploited?

CVE-2024-7419 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-7419 affect?

CVE-2024-7419 affects wp all export. Severity is high (CVSS 8.3). 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.

How urgent is CVE-2024-7419?

Priority 41/100. High severity

Software pages

WordPress vulnerabilities · PHP vulnerabilities

Related CVEs

CVE-2024-7425 MEDIUM 6.8 UPGRADE The WP ALL Export Pro plugin for WordPress is vulnerable to unauthorized modification of data that can lead to

References

← Back to latest CVEs