CVE-2020-24913: A SQL injection vulnerability in qcubed (all versions including 3.1.1) in profile.php via the strQuery para...
A SQL injection vulnerability in qcubed (all versions including 3.1.1) in profile.php via the strQuery parameter allows an unauthenticated attacker to access the database by injecting SQL code via a crafted POST request.
Security readout for executives and security teams
CVE-2020-24913 is an unauthenticated SQL injection issue in QCubed, reported in all versions including 3.1.1. An attacker can send a crafted POST request to profile.php and potentially access database contents. No source provided confirms active exploitation, but public advisories and exploit references exist. Organizations are exposed if they run QCubed applications containing the vulnerable profile.php endpoint, especially if reachable from untrusted networks. Exposure is unclear where QCubed is embedded inside custom applications, so inventory and application review are required. Prioritize discovery and containment for internet-facing QCubed applications. The business risk is potential database exposure without authentication. Treat as high priority where sensitive data is accessible through affected applications. Mitigation focus: Identify applications using QCubed, including embedded framework copies.; Check vendor or project guidance for fixed versions or official remediation.; Restrict external access to vulnerable profile.php where business permits..
Prepared
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.
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.
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
3Timeline events
1ADP providers
3Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Mar 4, 2021, 12:31 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.