CVE-2015-7682

Pie Register – User Registration Forms < 2.0.19 - Authenticated SQL Injection

2015-10-12 00:00
David Moore

Strategic Overview

Status
Patched in 2.0.19
Affected Version
< 2.0.19
CVSS
6.3Medium
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2015-7682
View all Pie Register – User Registration, Profiles & Content Restriction vulnerabilities

At a glance

CVE-2015-7682 is a medium-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Pie Register WordPress plugin, affecting versions < 2.0.19. It carries a CVSS score of 6.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account. The issue is fixed in version 2.0.19; sites on affected versions should update now. Disclosed October 2015, reported by David Moore.

Vulnerability Overview

Multiple SQL injection vulnerabilities in pie-register/pie-register.php in the Pie Register plugin before 2.0.19 for WordPress allow remote administrators to execute arbitrary SQL commands via the (1) select_invitaion_code_bulk_option or (2) invi_del_id parameter in the pie-invitation-codes page to wp-admin/admin.php.

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.

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

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

Remediation

Update to version 2.0.19, or a newer patched version

How does WordSec protect against this?

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