CVE-2021-24484

Secure Copy Content Protection and Content Locking <= 2.6.6 - SQL Injection

2021-06-29 00:00
To Quang Duong

Strategic Overview

Status
Patched in 2.6.7
Affected Plugin
Secure Copy Content Protection and Content Locking
Affected Version
< 2.6.7
CVSS
7.2High
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2021-24484
View all Secure Copy Content Protection and Content Locking vulnerabilities

At a glance

CVE-2021-24484 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Secure Copy Content Protection and Content Locking WordPress plugin, affecting versions < 2.6.7. 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 2.6.7; sites on affected versions should update now. Disclosed June 2021, reported by To Quang Duong.

Vulnerability Overview

The get_reports() function in the Secure Copy Content Protection and Content Locking WordPress plugin before 2.6.7 did not use whitelist or validate the orderby parameter before using it in SQL statements passed to the get_results() DB calls, leading to SQL injection issues in the admin dashboard

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

Secure Copy Content Protection and Content Locking < 2.6.7 carries this weakness at get_reports(), 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 Secure Copy Content Protection and Content Locking the fix is 2.6.7: builds < 2.6.7 are affected, anything from 2.6.7 onward is not.

Remediation

Update to version 2.6.7, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Secure Copy Content Protection and Content Locking: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Secure Copy Content Protection and Content Locking 2.6.7 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2021-24484https://www.wordfence.com/threat-intel/vulnerabilities/id/bbc1b46e-139a-4e1a-a0c7-e45e10adada5https://nvd.nist.gov/vuln/detail/CVE-2021-24484

Related records

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