CVE-2017-18515

WP Statistics <= 12.0.7 - Authenticated SQL Injection

2017-06-30 00:00
Anonymous

Strategic Overview

Status
Patched in 12.0.8
Affected Version
<= 12.0.7
CVSS
8.8High
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2017-18515
View all WP Statistics – Simple, privacy-friendly Google Analytics alternative vulnerabilities

At a glance

CVE-2017-18515 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the WP Statistics WordPress plugin, affecting versions <= 12.0.7. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account. The issue is fixed in version 12.0.8; sites on affected versions should update now. Disclosed June 2017.

Vulnerability Overview

The wp-statistics plugin before 12.0.8 for WordPress has 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 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 Statistics <= 12.0.7 takes any authenticated account. 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 Statistics the fix is 12.0.8: builds <= 12.0.7 are affected, anything from 12.0.8 onward is not.

Remediation

Update to version 12.0.8, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WP Statistics: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Statistics 12.0.8 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