CVE-2023-4724

Export any WordPress data to XML/CSV < 1.4.1 & WP ALL Export Pro < 1.8.6 - Authenticated (Admin+) Remote Code Execution

2023-11-24 00:00
Donato Di Pasquale

Strategic Overview

Status
Patched in 1.4.1
Affected Plugin
WP All Export – Drag & Drop Export to Any Custom CSV, XML & Excel
Affected Version
< 1.4.1
CVSS
6.4Medium
Weakness type
CWE-94 · Improper Control of Generation of Code ('Code Injection')
CVE
CVE-2023-4724
View all WP All Export – Drag & Drop Export to Any Custom CSV, XML & Excel vulnerabilities

At a glance

CVE-2023-4724 is a medium-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the WP All Export WordPress plugin, affecting versions < 1.4.1. It carries a CVSS score of 6.4 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Admin level or above. The issue is fixed in version 1.4.1; sites on affected versions should update now. Disclosed November 2023, reported by Donato Di Pasquale.

Vulnerability Overview

The Export any WordPress data to XML/CSV plugin for WordPress is vulnerable to Remote Code Execution in versions up to 1.4.1, and in versions up to 1.8.6 in the PRO version via the 'wp_query' parameter. This makes it possible for authenticated attackers, with administrator-level access and above, to execute code on the server.

Technical Analysis

The vector marks this flaw as remotely reachable over the network. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-94: Improper Control of Generation of Code ('Code Injection')

WP All Export < 1.4.1 carries this weakness at wp_query, and reaching it takes an account at Admin level or above. 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 the fix is 1.4.1: builds < 1.4.1 are affected, anything from 1.4.1 onward is not.

Remediation

Update to version 1.4.1, or a newer patched version

How does WordSec protect against this?

An attacker needs Admin access first, so the firewall sees the attempt as traffic from a logged-in account: 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 1.4.1 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-4724https://www.wordfence.com/threat-intel/vulnerabilities/id/43f976ee-cba7-4f5d-b9c6-a6f66c0011d2https://nvd.nist.gov/vuln/detail/CVE-2023-4724

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C