CVE-2021-24714

Import any XML or CSV File to WordPress <= 3.6.2 - Authenticated Stored Cross-Site Scripting

2021-11-02 00:00
Huy Nguyen

Strategic Overview

Status
Patched in 3.6.3
Affected Version
< 3.6.3
CVSS
4.8Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2021-24714
View all WP All Import – Drag & Drop Import for CSV, XML, Excel & Google Sheets vulnerabilities

At a glance

CVE-2021-24714 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the WP All Import WordPress plugin, affecting versions < 3.6.3. It carries a CVSS score of 4.8 (reachable over the network; low attack complexity). Exploitation requires an authenticated account. The issue is fixed in version 3.6.3; sites on affected versions should update now. Disclosed November 2021, reported by Huy Nguyen.

Vulnerability Overview

The Import any XML or CSV File to WordPress plugin before 3.6.3 does not escape the Import's Title and Unique Identifier fields before outputting them in admin pages, which could allow high privilege users to perform Cross-Site attacks even when the unfiltered_html capability is disallowed.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed.

CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Reaching this weakness in WP All Import < 3.6.3 takes any authenticated account. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.

Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For WP All Import the fix is 3.6.3: builds < 3.6.3 are affected, anything from 3.6.3 onward is not.

Remediation

Update to version 3.6.3, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WP All Import: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP All Import 3.6.3 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

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