CVE-2015-9462

Awesome Filterable Portfolio < 1.9 - Blind SQL Injection

2015-07-07 00:00
Marcin Probola

Strategic Overview

Status
Patched in 1.9
Affected Version
< 1.9
CVSS
7.2High
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2015-9462
View all Awesome Filterable Portfolio vulnerabilities

At a glance

CVE-2015-9462 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Awesome Filterable Portfolio WordPress plugin, affecting versions < 1.9. 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 1.9; sites on affected versions should update now. Disclosed July 2015, reported by Marcin Probola.

Vulnerability Overview

The awesome-filterable-portfolio plugin before 1.9 for WordPress has afp_get_new_category_page SQL injection via the cat_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 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 Awesome Filterable Portfolio < 1.9 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 Awesome Filterable Portfolio the fix is 1.9: builds < 1.9 are affected, anything from 1.9 onward is not.

Remediation

Update to version 1.9, or a newer patched version

How does WordSec protect against this?

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