CVE-2016-11000

Export WordPress Data with Advanced Filters < 1.2 - SQL Injection

2016-02-25 00:00
Henri Salo (fgeek)

Strategic Overview

Status
Patched in 1.2
Affected Version
<= 1.1
CVSS
9.8Critical
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2016-11000
View all Export All Posts, Products, Orders & Users | WP Ultimate Exporter | WordPress CSV Export vulnerabilities

At a glance

CVE-2016-11000 is a critical-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Export All Posts, Products, Orders & Users WordPress plugin, affecting versions <= 1.1. 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 1.2; sites on affected versions should update now. Disclosed February 2016, reported by Henri Salo (fgeek).

Vulnerability Overview

The wp-ultimate-exporter plugin through 1.1 for WordPress has SQL injection via the export_type_name parameter.

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 Export All Posts, Products, Orders & Users <= 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 Export All Posts, Products, Orders & Users the fix is 1.2: builds <= 1.1 are affected, anything from 1.2 onward is not.

Remediation

Update to version 1.2, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Export All Posts, Products, Orders & Users: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Export All Posts, Products, Orders & Users 1.2 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