CVE-2014-2316

Search Everything <= 7.0.2 - SQL Injection

2014-02-11 00:00
Anonymous

Strategic Overview

Status
Patched in 7.0.3
Affected Plugin
Search Everything
Affected Version
< 7.0.3
CVSS
9.1Critical
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2014-2316
View all Search Everything vulnerabilities

At a glance

CVE-2014-2316 is a critical-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Search Everything WordPress plugin, affecting versions < 7.0.3. It carries a CVSS score of 9.1 (reachable over the network; low attack complexity; high confidentiality, integrity impact). Exploitation requires no authentication. The issue is fixed in version 7.0.3; sites on affected versions should update now. Disclosed February 2014.

Vulnerability Overview

SQL injection vulnerability in se_search_default in the Search Everything plugin before 7.0.3 for WordPress allows remote attackers to execute arbitrary SQL commands via the s parameter to index.php. NOTE: some of these details are obtained from third party information.

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.

CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Reaching this weakness in Search Everything < 7.0.3 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 Search Everything the fix is 7.0.3: builds < 7.0.3 are affected, anything from 7.0.3 onward is not.

Remediation

Update to version 7.0.3, or a newer patched version

How does WordSec protect against this?

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