WP All Export Pro <= 1.9.1 - Unauthenticated Remote Code Execution via Custom Export Fields
Strategic Overview
- Status
- Patched in 1.9.2
- Affected Plugin
- WP All Export Pro
- Affected Version
<= 1.9.1- CVSS
- 8.3High
- Weakness type
- CWE-94 · Improper Control of Generation of Code ('Code Injection')
- CVE
CVE-2024-7419
At a glance
CVE-2024-7419 is a high-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the WP All Export Pro WordPress plugin, affecting versions <= 1.9.1. It carries a CVSS score of 8.3 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.9.2; sites on affected versions should update now. Disclosed February 2025, reported by Francesco Carlucci.
Vulnerability Overview
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 Analysis
The vector marks this flaw as remotely reachable over the network, and no privileges on the target site. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-94: Improper Control of Generation of Code ('Code Injection')
Reaching this weakness in WP All Export Pro <= 1.9.1 takes no account at all. Code injection means input from a request reaches a language construct that evaluates code, so the attacker's text is executed rather than treated as data.
The injected code runs with the web server's privileges, giving the attacker the same access to the database and filesystem as WordPress itself. For WP All Export Pro the fix is 1.9.2: builds <= 1.9.1 are affected, anything from 1.9.2 onward is not.
Remediation
Update to version 1.9.2, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: WP All Export Pro 1.9.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Login Security
External References
Related records
Same weakness class
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C