Export any WordPress data to XML/CSV <= 1.3.4 - Authenticated SQL Injection
Strategic Overview
- Status
- Patched in 1.3.5
- Affected Version
<= 1.3.4- CVSS
- 9.0Critical
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2022-1800
At a glance
CVE-2022-1800 is a critical-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the WP All Export WordPress plugin, affecting versions <= 1.3.4. It carries a CVSS score of 9.0 (reachable over the network; low attack complexity; high confidentiality, integrity impact). Exploitation requires an authenticated account. The issue is fixed in version 1.3.5; sites on affected versions should update now. Disclosed May 2022, reported by Asif Nawaz Minhas.
Vulnerability Overview
The Export any WordPress data to XML/CSV WordPress plugin before 1.3.5 does not sanitize the cpt POST parameter when exporting post data before using it in a database query, leading to an SQL injection vulnerability.
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.
CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Reaching this weakness in WP All Export <= 1.3.4 takes any authenticated account. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.
A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For WP All Export the fix is 1.3.5: builds <= 1.3.4 are affected, anything from 1.3.5 onward is not.
Remediation
Update to version 1.3.5, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to WP All Export: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP All Export 1.3.5 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in WP All Export – Drag & Drop Export to Any Custom CSV, XML & Excel
- 8.8CVE-2023-5882: Export any… & WP ALL Export Pro < 1.8.6 - CSRF
CVE-2023-5882 - 8.8CVE-2023-5886: Export any… & WP ALL Export Pro < 1.8.6 - CSRF
CVE-2023-5886 - 6.4CVE-2023-4724: Export any WordPress data… & WP ALL Export Pro < 1.8.6
CVE-2023-4724 - 6.1Export any WordPress data to XML/CSV <= 1.3.5 Reflected XSS
- 4.8CVE-2021-24708: WP All Export <= 1.3.0 Admin+ Stored XSS
CVE-2021-24708 - 3.7CVE-2026-1582: WP All Export <= 1.4.14 Sensitive Information Exposure
CVE-2026-1582
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C