CVE-2015-2213

WordPress Core < 4.2.4 - SQL Injection

2015-08-04 00:00
Anonymous

Strategic Overview

Status
Patched in 3.7.10
Affected Core
WordPress 4.2
Affected Version
3.7 – 4.2.3 · 7 branches
CVSS
8.8High
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2015-2213
View all WordPress 4.2 vulnerabilities

At a glance

CVE-2015-2213 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the WordPress 4.2 WordPress release line, affecting 3.7 – 4.2.3 · 7 branches. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 3.7.10; sites on affected versions should update now. Disclosed August 2015.

Vulnerability Overview

SQL injection vulnerability in the wp_untrash_post_comments function in wp-includes/post.php in WordPress before 4.2.4 allows remote attackers to execute arbitrary SQL commands via a comment that is mishandled after retrieval from the trash.

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 WordPress 4.2 3.7 – 4.2.3 · 7 branches 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 WordPress 4.2 the fix is 3.7.10: builds 3.7 – 4.2.3 · 7 branches are affected, anything from 3.7.10 onward is not.

Remediation

Update to one of the following versions, or a newer patched version: 3.7.10, 3.8.10, 3.9.8, 4.0.7, 4.1.7, 4.2.4

How does WordSec protect against this?

The attempt arrives as an ordinary request to WordPress 4.2: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: updating to 3.7.10 is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2015-2213https://www.wordfence.com/threat-intel/vulnerabilities/id/c6ae2633-caf6-4319-ba81-e71a673c89eehttps://nvd.nist.gov/vuln/detail/CVE-2015-2213

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C