CVE-2015-9353

GigPress <= 2.3.10 - SQL Injection

2015-08-24 00:00
Marcin Probola

Strategic Overview

Status
Patched in 2.3.11
Affected Plugin
GigPress
Affected Version
< 2.3.11
CVSS
7.2High
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2015-9353
View all GigPress vulnerabilities

At a glance

CVE-2015-9353 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the GigPress WordPress plugin, affecting versions < 2.3.11. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 2.3.11; sites on affected versions should update now. Disclosed August 2015, reported by Marcin Probola.

Vulnerability Overview

The gigpress plugin before 2.3.11 for WordPress has SQL injection in the admin area, a different vulnerability than CVE-2015-4066.

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

Remediation

Update to version 2.3.11, or a newer patched version

How does WordSec protect against this?

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