LiveActive security incident?Get immediate response
CVE Record

CVE-2021-24484: Secure Copy Content Protection and Content Locking < 2.6.7 - Authenticated Blind SQL Injections

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

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This affects a WordPress plugin used to protect or lock site content. In versions before 2.6.7, an authenticated user reaching the plugin’s admin reporting function could influence database queries through an unvalidated sorting parameter. That creates a blind SQL injection risk, but the provided sources do not give CVSS, exploitation, or role details.

Executive priority

Treat as a timely patching item for affected WordPress properties, especially business-critical sites. It is not KEV-listed in the provided data, but SQL injection can threaten database confidentiality and integrity if an attacker has the needed authenticated access.

Technical view

CVE-2021-24484 is CWE-89 in Secure Copy Content Protection and Content Locking before 2.6.7. The get_reports() function used the orderby parameter in SQL passed to get_results() without whitelisting or validation, enabling authenticated blind SQL injection in the admin dashboard.

Likely exposure

Exposure is limited to WordPress sites running the Ays Pro Secure Copy Content Protection and Content Locking plugin before 2.6.7, where an authenticated user can access the affected admin reporting path. The exact required privilege level is not stated in the provided bundle.

Exploitation context

The source bundle marks KEV as false and provides no cited evidence of active exploitation. The issue is authenticated and blind, so successful abuse likely depends on dashboard access and database-query side effects rather than public unauthenticated access.

Researcher notes

The key uncertainty is authorization scope. Sources state authenticated admin-dashboard SQL injection through orderby in get_reports(), but do not specify the minimum WordPress role, CVSS vector, exploit maturity, or complete patch details beyond the before-2.6.7 boundary.

Mitigation direction

  • Upgrade the plugin to version 2.6.7 or later.
  • If immediate upgrade is impossible, disable the plugin temporarily.
  • Restrict WordPress admin access to trusted users only.
  • Review vendor and WPScan guidance for any later advisories.
  • Monitor admin activity and database anomalies after remediation.

Validation and detection

  • Inventory WordPress sites for the affected plugin.
  • Confirm installed plugin versions are 2.6.7 or later.
  • Identify users who can access the plugin admin dashboard.
  • Review web and WordPress logs for unusual admin report requests.
  • Verify no unexpected database or content changes occurred.
Prepared
Confidence
medium
Sources
3

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-24484 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Ays ProSecure Copy Content Protection and Content Locking2.6.7Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.