CVE-2017-1002026

Event Expresso Free <= 3.1.37.11.L - Authenticated SQL Injection

2017-07-04 00:00
Larry W. Cashdollar

Strategic Overview

Status
Patched in 3.1.37.12.L
Affected Plugin
Event Expresso Free
Affected Version
<= 3.1.37.11.L
CVSS
8.8High
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2017-1002026
View all Event Expresso Free vulnerabilities

At a glance

CVE-2017-1002026 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Event Expresso Free WordPress plugin, affecting versions <= 3.1.37.11.L. 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 3.1.37.12.L; sites on affected versions should update now. Disclosed July 2017, reported by Larry W. Cashdollar.

Vulnerability Overview

Vulnerability in wordpress plugin Event Expresso Free v3.1.37.11.L, The function edit_event_category does not sanitize user-supplied input via the $id parameter before passing it into an SQL statement.

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 Event Expresso Free <= 3.1.37.11.L 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 Event Expresso Free the fix is 3.1.37.12.L: builds <= 3.1.37.11.L are affected, anything from 3.1.37.12.L onward is not.

Remediation

Update to version 3.1.37.12.L, or a newer patched version

How does WordSec protect against this?

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