CVE-2014-10387

Support Plus Responsive Ticket System <= 4.1 - SQL Injection

2014-09-09 00:00
Fikri Fadzil

Strategic Overview

Status
Patched in 4.2
Affected Version
< 4.2
CVSS
9.8Critical
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2014-10387
View all WP Support Plus Responsive Ticket System vulnerabilities

At a glance

CVE-2014-10387 is a critical-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the WP Support Plus Responsive Ticket System WordPress plugin, affecting versions < 4.2. 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 4.2; sites on affected versions should update now. Disclosed September 2014, reported by Fikri Fadzil.

Vulnerability Overview

The Support Plus Responsive Ticket System plugin before 4.2 for WordPress has SQL injection.

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 WP Support Plus Responsive Ticket System < 4.2 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 WP Support Plus Responsive Ticket System the fix is 4.2: builds < 4.2 are affected, anything from 4.2 onward is not.

Remediation

Update to version 4.2, or a newer patched version

How does WordSec protect against this?

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