Top 10 – Popular posts plugin for WordPress <= 2.4.3 - SQL Injection

2017-12-13 00:00
DefenceCode

Strategic Overview

Status
Patched in 2.4.4
Affected Plugin
WebberZone Top 10 — Popular Posts
Affected Version
< 2.4.4
CVSS
7.4High
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE pending
View all WebberZone Top 10 — Popular Posts vulnerabilities

At a glance

This record tracks a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the WebberZone Top 10 WordPress plugin, affecting versions < 2.4.4. It carries a CVSS score of 7.4 (reachable over the network; low attack complexity). The issue is fixed in version 2.4.4; sites on affected versions should update now. Disclosed December 2017, reported by DefenceCode.

Vulnerability Overview

The Top 10 – Popular posts plugin for WordPress plugin for WordPress is vulnerable to generic SQL Injection via the ‘get_results’ parameter in versions up to, and including, 2.4.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 authenticated attackers with admin level access 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 interaction from a victim user.

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

WebberZone Top 10 < 2.4.4 carries this weakness at get_results, 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 WebberZone Top 10 the fix is 2.4.4: builds < 2.4.4 are affected, anything from 2.4.4 onward is not.

Remediation

Update to version 2.4.4, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WebberZone Top 10: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WebberZone Top 10 2.4.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/9b320755-1255-4331-8176-ee67d8d4873e

Related records

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