WP ALL Export Pro <= 1.7.8 - Authenticated Remote Code Execution
Strategic Overview
- Status
- Patched in 1.7.9
- Affected Plugin
- WP All Export Pro
- Affected Version
<= 1.7.8- CVSS
- 8.8High
- Weakness type
- CWE-94 · Improper Control of Generation of Code ('Code Injection')
- CVE
CVE-2022-3394
At a glance
CVE-2022-3394 is a high-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the WP All Export Pro WordPress plugin, affecting versions <= 1.7.8. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account. The issue is fixed in version 1.7.9; sites on affected versions should update now. Disclosed October 2022, reported by Sanjay Das Payatu.
Vulnerability Overview
The WP ALL Export Pro plugin for WordPress is vulnerable to Remote Code Execution in versions up to, and including, 1.7.8. This allows low-level attackers (depending on whether they have been given permission to perform exports) to execute code on the server. While the plugin defaults to allow only administrators to perform such exports, they can also delegate this task to lower-privileged users.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. 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.7.8 takes any authenticated account. 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.7.9: builds <= 1.7.8 are affected, anything from 1.7.9 onward is not.
Remediation
Update to version 1.7.9, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to WP All Export Pro: 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.7.9 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Related records
Same weakness class
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C