CVE-2021-24931

Secure Copy Content Protection and Content Locking <= 2.8.1 - Unauthenticated SQL Injection

2021-11-08 00:00
Krzysztof Zając

Strategic Overview

Status
Patched in 2.8.2
Affected Plugin
Secure Copy Content Protection and Content Locking
Affected Version
<= 2.8.1
CVSS
9.8Critical
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2021-24931
View all Secure Copy Content Protection and Content Locking vulnerabilities

At a glance

CVE-2021-24931 is a critical-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.8.1. 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.8.2; sites on affected versions should update now. Disclosed November 2021, reported by Krzysztof Zając.

Vulnerability Overview

The Secure Copy Content Protection and Content Locking WordPress plugin before 2.8.2 does not escape the sccp_id parameter of the ays_sccp_results_export_file AJAX action (available to both unauthenticated and authenticated users) before using it in a SQL statement, leading to an SQL injection.

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 Secure Copy Content Protection and Content Locking <= 2.8.1 takes no account at all. 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.8.2: builds <= 2.8.1 are affected, anything from 2.8.2 onward is not.

Remediation

Update to version 2.8.2, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: 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.8.2 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2021-24931https://www.wordfence.com/threat-intel/vulnerabilities/id/0b52cc2a-c511-4801-8a95-f90d8d980c85https://nvd.nist.gov/vuln/detail/CVE-2021-24931

Related records

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