WP eCommerce < 3.11.4 - SQL Injection

2016-11-12 00:00

Strategic Overview

Status: Patched in 3.11.4
Affected Plugin: WP eCommerce
Affected Version: < 3.11.4
CVSS: 8.3High
Weakness type: CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE: CVE pending

At a glance

This record tracks a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the WP eCommerce WordPress plugin, affecting versions < 3.11.4. It carries a CVSS score of 8.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.11.4; sites on affected versions should update now. Disclosed November 2016, reported by Mika Epstein.

Vulnerability Overview

The WP eCommerce plugin for WordPress is vulnerable to SQL Injection via the ‘sessionid’ parameter in versions up to, and including, 3.11.3 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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.

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

WP eCommerce < 3.11.4 carries this weakness at sessionid, and reaching it 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 eCommerce the fix is 3.11.4: builds < 3.11.4 are affected, anything from 3.11.4 onward is not.

Remediation

Update to version 3.11.4, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WP eCommerce: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP eCommerce 3.11.4 closes this, and updating the plugin is the step that ends it.

Firewall
Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/3c43939f-c0c7-4388-80ae-44bdf67675c7

Related records

Same weakness class

Other vulnerabilities in WP eCommerce

CVSS Vector

8.3

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeChanged
ConfidentialityLow
IntegrityLow
AvailabilityLow

This record contains material that is subject to copyright

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/