Import any XML or CSV File to WordPress <= 3.2.4 - SQL Injection

2020-02-19 00:00
Kacper Szurek

Strategic Overview

Status
Patched in 4.1.2
Affected Plugin
WP All Import Pro
Affected Version
<= 4.1.1
CVSS
7.2High
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE pending
View all WP All Import Pro vulnerabilities

At a glance

This record tracks a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the WP All Import Pro WordPress plugin, affecting versions <= 4.1.1. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 4.1.2; sites on affected versions should update now. Disclosed February 2020, reported by Kacper Szurek.

Vulnerability Overview

The Import any XML or CSV File to WordPress plugin for WordPress is vulnerable to SQL Injection via an unknown parameter in versions up to, and including, 3.2.4 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers with administrative capabilities and above to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Reaching this weakness in WP All Import Pro <= 4.1.1 takes a caller who can reach the endpoint. 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 Import Pro the fix is 4.1.2: builds <= 4.1.1 are affected, anything from 4.1.2 onward is not.

Remediation

Update to version 4.1.2, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/52d390e0-95ca-4570-8d4c-f679ee86ffea

Related records

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