WordPress Automatic Plugin <= 2.0.3 - Cross-Site Request Forgery to SQL Injection

2014-08-01 00:00
NICK58

Strategic Overview

Status
Patched in 2.0.4
Affected Plugin
WordPress Automatic Plugin
Affected Version
<= 2.0.3
CVSS
9.8Critical
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE pending
View all WordPress Automatic Plugin vulnerabilities

At a glance

This record tracks a critical-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the WordPress Automatic Plugin WordPress plugin, affecting versions <= 2.0.3. 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 2.0.4; sites on affected versions should update now. Disclosed August 2014, reported by NICK58.

Vulnerability Overview

The "WordPress Automatic Plugin" plugin for WordPress is vulnerable to generic SQL Injection via the ‘q’ parameter in versions up to, and including, 2.0.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. 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 Automatic Plugin <= 2.0.3 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 Automatic Plugin the fix is 2.0.4: builds <= 2.0.3 are affected, anything from 2.0.4 onward is not.

Remediation

Update to version 2.0.4, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WordPress Automatic Plugin: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WordPress Automatic Plugin 2.0.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/fa45d830-fa28-4d94-a6d5-2dc2b8456cf2

Related records

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