CVE-2021-24786

Download Monitor <= 4.4.4 - Admin+ SQL Injection via orderby parameter

2021-10-20 00:00
bl4derunner

Strategic Overview

Status
Patched in 4.4.5
Affected Plugin
Download Monitor
Affected Version
< 4.4.5
CVSS
7.2High
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2021-24786
View all Download Monitor vulnerabilities

At a glance

CVE-2021-24786 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Download Monitor WordPress plugin, affecting versions < 4.4.5. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 4.4.5; sites on affected versions should update now. Disclosed October 2021, reported by bl4derunner.

Vulnerability Overview

The Download Monitor WordPress plugin before 4.4.5 does not properly validate and escape the "orderby" GET parameter before using it in a SQL statement when viewing the logs, leading to an SQL Injection issue

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')

Download Monitor < 4.4.5 carries this weakness at orderby, 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 Download Monitor the fix is 4.4.5: builds < 4.4.5 are affected, anything from 4.4.5 onward is not.

Remediation

Update to version 4.4.5, or a newer patched version

How does WordSec protect against this?

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