CVE-2020-24913

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 40.6%, top 1% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 41%CVSS: 9.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
65(Track*)
EG Risk 65/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation41% × 40%
Automatability30% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
41%
EPSS %ILE
99%
KEV
Not listed

Published

March 4, 2021

Last Modified

July 9, 2026

Advisory Details (6)

Auto-updated Aug 16, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic

Sicherheitsüberprüfung / Security Check

https://www.ait.ac.at/themen/cyber-security/pentesting/security-advisories/ait-sa-20210215-02
generic

QCubed SQL Injection ( CVE-2020-24913) | FYHTECH

https://tech.feedyourhead.at/content/QCubed-SQL-Injection-CVE-2020-24913
generic🟡 PoC Available

Full Disclosure: [AIT-SA-20210215-03] CVE-2020-24912: QCube Cross-Site-Scripting

http://seclists.org/fulldisclosure/2021/Mar/30
generic

Full Disclosure: [AIT-SA-20210215-02] CVE-2020-24913: QCubed SQL Injection

http://seclists.org/fulldisclosure/2021/Mar/29
generic

Locked Out | Packet Storm

http://packetstormsecurity.com/files/161759/QCubed-3.1.1-SQL-Injection.html
generic

Qcubed.com - Ready for Development

http://qcubed.com

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFixed inDependents
qcubed/qcubedv3.0.1-beta ... v3.1.1 (11 versions)3.2—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 113 total refreshes for this CVE.

  1. 2026-08-20 22:52 UTCEPSS rescore
  2. 2026-08-20 07:25 UTCOSV refresh
  3. 2026-08-19 17:00 UTCEPSS rescore
  4. 2026-08-18 13:44 UTCEPSS rescore
  5. 2026-08-17 13:43 UTCEPSS rescore
  6. 2026-08-16 14:52 UTCEPSS rescore
  7. 2026-08-16 02:11 UTCEPSS rescore
  8. 2026-08-15 01:26 UTCEPSS rescore
  9. 2026-08-13 21:57 UTCEPSS rescore
  10. 2026-08-12 13:47 UTCEPSS rescore
  11. 2026-08-07 16:23 UTCEPSS rescore
  12. 2026-08-06 13:43 UTCEPSS rescore
  13. 2026-08-05 19:14 UTCEPSS rescore
  14. 2026-08-05 02:41 UTCOSV refresh
  15. 2026-08-04 15:06 UTCEPSS rescore
  16. 2026-08-03 10:32 UTCEPSS rescore
  17. 2026-08-01 04:12 UTCEPSS rescore
  18. 2026-07-30 16:25 UTCEPSS rescore
  19. 2026-07-30 01:27 UTCEPSS rescore
  20. 2026-07-28 15:32 UTCEPSS rescore
  21. 2026-07-26 14:51 UTCEPSS rescore
  22. 2026-07-25 14:15 UTCEPSS rescore
  23. 2026-07-25 14:14 UTCEPSS rescore
  24. 2026-07-24 14:14 UTCEPSS rescore
  25. 2026-07-23 14:15 UTCEPSS rescore
Show 75 more
  1. 2026-07-23 14:15 UTCEPSS rescore
  2. 2026-07-23 01:51 UTCEG score recompute
  3. 2026-07-22 22:37 UTCEG score recompute
  4. 2026-07-22 14:05 UTCEPSS rescore
  5. 2026-07-21 15:22 UTCEPSS rescore
  6. 2026-07-21 15:22 UTCEPSS rescore
  7. 2026-07-20 17:04 UTCEPSS rescore
  8. 2026-07-20 17:04 UTCEPSS rescore
  9. 2026-07-19 14:28 UTCEPSS rescore
  10. 2026-07-19 02:26 UTCEPSS rescore
  11. 2026-07-19 02:26 UTCEPSS rescore
  12. 2026-07-19 00:59 UTCOSV refresh
  13. 2026-07-18 10:02 UTCEPSS rescore
  14. 2026-07-16 16:59 UTCEPSS rescore
  15. 2026-07-15 16:55 UTCEPSS rescore
  16. 2026-07-13 22:27 UTCEPSS rescore
  17. 2026-07-13 22:27 UTCEPSS rescore
  18. 2026-07-13 06:10 UTCEPSS rescore
  19. 2026-07-13 06:10 UTCEPSS rescore
  20. 2026-07-12 05:44 UTCEPSS rescore
  21. 2026-07-11 08:25 UTCEPSS rescore
  22. 2026-07-11 08:25 UTCEPSS rescore
  23. 2026-07-09 19:07 UTCEPSS rescore
  24. 2026-07-09 00:54 UTCNVD updateCVSS v3 → 9.8 · severity → CRITICAL
  25. 2026-07-09 00:13 UTCMITRE cvelistV5
  26. 2026-07-08 15:12 UTCEPSS rescore
  27. 2026-07-06 16:25 UTCEPSS rescore
  28. 2026-07-06 16:25 UTCEPSS rescore
  29. 2026-07-06 02:21 UTCEPSS rescore
  30. 2026-07-06 02:21 UTCEPSS rescore
  31. 2026-07-05 02:27 UTCEPSS rescore
  32. 2026-07-05 00:28 UTCNVD updateCVSS v3 → 9.8 · severity → CRITICAL
  33. 2026-07-04 23:57 UTCMITRE cvelistV5
  34. 2026-07-01 15:03 UTCEPSS rescore
  35. 2026-07-01 07:48 UTCOSV refresh
  36. 2026-06-30 23:20 UTCEPSS rescore
  37. 2026-06-30 23:20 UTCEPSS rescore
  38. 2026-06-28 04:54 UTCEPSS rescore
  39. 2026-06-28 04:54 UTCEPSS rescore
  40. 2026-06-27 03:06 UTCEPSS rescore
  41. 2026-06-25 13:47 UTCEPSS rescore
  42. 2026-06-24 14:03 UTCEPSS rescore
  43. 2026-06-24 14:03 UTCEPSS rescore
  44. 2026-06-23 21:31 UTCEPSS rescore
  45. 2026-06-23 21:31 UTCEPSS rescore
  46. 2026-06-21 14:54 UTCEPSS rescore
  47. 2026-06-21 14:54 UTCEPSS rescore
  48. 2026-06-21 01:57 UTCEPSS rescore
  49. 2026-06-21 01:57 UTCEPSS rescore
  50. 2026-06-18 17:50 UTCEPSS rescore
  51. 2026-06-17 17:50 UTCEPSS rescore
  52. 2026-06-16 17:50 UTCEPSS rescore
  53. 2026-06-16 17:50 UTCEPSS rescore
  54. 2026-06-15 17:46 UTCEPSS rescore
  55. 2026-06-13 22:58 UTCEPSS rescore
  56. 2026-06-13 22:58 UTCEPSS rescore
  57. 2026-06-13 12:43 UTCOSV refresh
  58. 2026-06-12 23:10 UTCEPSS rescore
  59. 2026-06-11 13:58 UTCEPSS rescore
  60. 2026-06-10 22:16 UTCEPSS rescore
  61. 2026-06-10 22:16 UTCEPSS rescore
  62. 2026-06-10 13:20 UTCEPSS rescore
  63. 2026-06-08 14:15 UTCEPSS rescore
  64. 2026-06-08 14:15 UTCEPSS rescore
  65. 2026-06-07 15:23 UTCEPSS rescore
  66. 2026-06-07 15:23 UTCEPSS rescore
  67. 2026-06-06 13:45 UTCEPSS rescore
  68. 2026-06-06 13:45 UTCEPSS rescore
  69. 2026-06-05 22:45 UTCEPSS rescore
  70. 2026-06-05 22:45 UTCEPSS rescore
  71. 2026-06-05 06:08 UTCEPSS rescore
  72. 2026-06-05 06:08 UTCEPSS rescore
  73. 2026-06-04 13:10 UTCEPSS rescore
  74. 2026-06-04 13:10 UTCEPSS rescore
  75. 2026-06-02 20:11 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2020-24913?
CVE-2020-24913 is a critical vulnerability published on March 4, 2021. 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.
When was CVE-2020-24913 disclosed?
CVE-2020-24913 was first published in the National Vulnerability Database on March 4, 2021, with the most recent update on July 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-24913 actively exploited?
CVE-2020-24913 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 41% probability of exploitation in the next 30 days, which ranks it in the top 1.5% of all scored CVEs.
What is the CVSS score of CVE-2020-24913?
CVE-2020-24913 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2020-24913?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-24913, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-24913

Explore →

Is Your Infrastructure Affected by CVE-2020-24913?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs