CVE-2015-9330

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

2015-03-12 00:00
Anonymous

Strategic Overview

Status
Patched in 3.2.5
Affected Version
< 3.2.5
CVSS
9.8Critical
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2015-9330
View all WP All Import – Drag & Drop Import for CSV, XML, Excel & Google Sheets vulnerabilities

At a glance

CVE-2015-9330 is a critical-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the WP All Import WordPress plugin, affecting versions < 3.2.5. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.2.5; sites on affected versions should update now. Disclosed March 2015.

Vulnerability Overview

The wp-all-import plugin before 3.2.5 for WordPress has blind SQL injection.

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, 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 < 3.2.5 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 the fix is 3.2.5: builds < 3.2.5 are affected, anything from 3.2.5 onward is not.

Remediation

Update to version 3.2.5, 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.2.5 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