CVE-2023-5886

Export any WordPress data to XML/CSV < 1.4.1 & WP ALL Export Pro < 1.8.6 - Cross-Site Request Forgery to PHAR Deserialization

2023-11-24 00:00
Alex Sanford

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
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-5886
View all WP All Export – Drag & Drop Export to Any Custom CSV, XML & Excel vulnerabilities

At a glance

CVE-2023-5886 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP All Export WordPress plugin, affecting versions < 1.4.1. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.4.1; sites on affected versions should update now. Disclosed November 2023, reported by Alex Sanford.

Vulnerability Overview

The Export any WordPress data to XML/CSV plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to 1.4.1, and in versions up to 1.8.6 in the PRO version. This is due to missing nonce validation on a function. This makes it possible for unauthenticated attackers to perform unauthorized actions and deserialize a PHAR object and potentially achieve remote code execution via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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 privileges on the target site. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in WP All Export < 1.4.1 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. 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?

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.4.1 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-5886https://www.wordfence.com/threat-intel/vulnerabilities/id/fdc18341-135b-4522-a9db-510e4c4d9704https://nvd.nist.gov/vuln/detail/CVE-2023-5886

Related records

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