Skip to content
Fencer Intel
critical 9.8

CVE-2020-24913 in the critical feed json

qcubed SQL injection vulnerability in profile.php via the strQuery parameter

published 5y ago modified 4mo ago also GHSA-8fj6-pc5r-347q , EUVD-2022-3170

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
40.9%
EPSS 40.9% chance of exploitation in 30 days, percentile 98%
public exploits
0
none known

Summary

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.

Patch / fix

  • packagist qcubed/qcubed 3.2

Is CVE-2020-24913 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

40.89% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • ait.ac.at https://www.ait.ac.at/themen/cyber-security/pentesting/security-advisories/ait-sa-20210215-02 referenced PoC, tagged "exploit" by a source, unverified
  • tech.feedyourhead.at https://tech.feedyourhead.at/content/QCubed-SQL-Injection-CVE-2020-24913 referenced PoC, tagged "exploit" by a source, unverified
  • seclists.org http://seclists.org/fulldisclosure/2021/Mar/30 referenced PoC, tagged "exploit" by a source, unverified
  • seclists.org http://seclists.org/fulldisclosure/2021/Mar/29 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
packagist qcubed/qcubed
<3.2
3.2

Classification

Weakness
  • CWE-89 Improper Neutralization of Special Elements used in an SQL Command

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.