CVE-2016-10947

Post Indexer <= 3.0.6.1 - Authenticated (Super Admin+) SQL Injection

2016-11-17 00:00
Glyn Wintle

Strategic Overview

Status
Patched in 3.0.6.2
Affected Plugin
Post Indexer
Affected Version
< 3.0.6.2
CVSS
7.2High
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2016-10947
View all Post Indexer vulnerabilities

At a glance

CVE-2016-10947 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Post Indexer WordPress plugin, affecting versions < 3.0.6.2. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Super Admin level or above. The issue is fixed in version 3.0.6.2; sites on affected versions should update now. Disclosed November 2016, reported by Glyn Wintle.

Vulnerability Overview

The Post Indexer plugin before 3.0.6.2 for WordPress has SQL injection via the period parameter by a super admin.

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 Post Indexer < 3.0.6.2 takes an account at Super Admin level or above. 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 Post Indexer the fix is 3.0.6.2: builds < 3.0.6.2 are affected, anything from 3.0.6.2 onward is not.

Remediation

Update to version 3.0.6.2, or a newer patched version

How does WordSec protect against this?

An attacker needs Super Admin access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Post Indexer 3.0.6.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