CVE-2016-10904

Olimometer < 2.57 - SQL Injection

2016-11-22 00:00
TAD Group

Strategic Overview

Status
Patched in 2.57
Affected Plugin
Olimometer
Affected Version
< 2.57
CVSS
9.8Critical
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2016-10904
View all Olimometer vulnerabilities

At a glance

CVE-2016-10904 is a critical-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Olimometer WordPress plugin, affecting versions < 2.57. 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 2.57; sites on affected versions should update now. Disclosed November 2016, reported by TAD Group.

Vulnerability Overview

The olimometer plugin before 2.57 for WordPress has SQL injection via olimometer_id 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 Olimometer < 2.57 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 Olimometer the fix is 2.57: builds < 2.57 are affected, anything from 2.57 onward is not.

Remediation

Update to version 2.57, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

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