CVE-2012-5327

Mingle Forum <= 1.0.32.1 - SQL Injection

2014-08-01 00:00
Gianluca Brindisi

Strategic Overview

Status
Patched in 1.0.33
Affected Plugin
Mingle Forum
Affected Version
<= 1.0.32.1
CVSS
8.8High
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2012-5327
View all Mingle Forum vulnerabilities

At a glance

CVE-2012-5327 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Mingle Forum WordPress plugin, affecting versions <= 1.0.32.1. 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 1.0.33; sites on affected versions should update now. Disclosed August 2014, reported by Gianluca Brindisi.

Vulnerability Overview

Multiple SQL injection vulnerabilities in fs-admin/fs-admin.php in the Mingle Forum plugin 1.0.32.1 and other versions before 1.0.33 for WordPress allow remote authenticated users to execute arbitrary SQL commands via the (1) delete_usrgrp[] parameter in a delete_usergroups action, (2) usergroup parameter in an add_user_togroup action, or (3) add_forum_group_id parameter in an add_forum_submit action.

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 Mingle Forum <= 1.0.32.1 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 Mingle Forum the fix is 1.0.33: builds <= 1.0.32.1 are affected, anything from 1.0.33 onward is not.

Remediation

Update to version 1.0.33, or a newer patched version

How does WordSec protect against this?

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