CVE-2021-39179

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 1.9%, top 23% 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
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2%CVSS: 8.8Exploit: None knownExposed: 0

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

DHIS 2 is an information system for data capture, management, validation, analytics and visualization. A SQL Injection vulnerability in the Tracker component in DHIS2 Server allows authenticated remote attackers to execute arbitrary SQL commands via unspecified vectors. This vulnerability affects the /api/trackedEntityInstances and /api/trackedEntityInstances/query API endpoints in all DHIS2 versions 2.34, 2.35, and 2.36. It also affects versions 2.32 and 2.33 which have reached _end of support_ - exceptional security updates have been added to the latest *end of support* builds for these versions. Versions 2.31 and older are unaffected. The system is vulnerable to attack only from users that are logged in to DHIS2, and there is no known way of exploiting the vulnerability without first being logged in as a DHIS2 user. The vulnerability is not exposed to a non-malicious user - the vulnerability requires a conscious attack to be exploited. A successful exploit of this vulnerability could allow the malicious user to read, edit and delete data in the DHIS2 instance. There are no known exploits of the security vulnerabilities addressed by these patch releases. Security patches are available in DHIS2 versions 2.32-EOS, 2.33-EOS, 2.34.7, 2.35.7, and 2.36.4. There is no straightforward known workaround for DHIS2 instances using the Tracker functionality other than upgrading the affected DHIS2 server to one of the patches in which this vulnerability has been fixed. For implementations which do NOT use Tracker functionality, it may be possible to block all network access to POST to the /api/trackedEntityInstances, and /api/trackedEntityInstances/query endpoints as a temporary workaround while waiting to upgrade.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
45(Track)
EG Risk 45/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
Severity88% × 45%
Exploitation2% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
2%
EPSS %ILE
79%
KEV
Not listed

Published

October 29, 2021

Last Modified

November 21, 2024

Advisory Details (3)

Auto-updated Aug 25, 2026
Patch available. Sources: github_commit, github_pr, github.
github Patch Available

SQL Injection in DHIS2 Tracker API (assignedUsers and escapeSql) · Advisory · dhis2/dhis2-core · GitHub

https://github.com/dhis2/dhis2-core/security/advisories/GHSA-cmpc-frjv-rrmw
github_pr

build: correct patch PRs

Fix merged in dhis2/dhis2-core PR #8771 on 2021-09-20 — awaiting tagged release

https://github.com/dhis2/dhis2-core/pull/8771
github_commit

commit 16674ac75127 (dhis2/dhis2-core)

Fix landed in dhis2/dhis2-core commit 16674ac75127 — awaiting tagged release

https://github.com/dhis2/dhis2-core/commit/16674ac75127b0e83691c6b1c9ce745e67ab58b6

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 33× 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 154 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2021-39179?
CVE-2021-39179 is a high vulnerability published on October 29, 2021. DHIS 2 is an information system for data capture, management, validation, analytics and visualization. A SQL Injection vulnerability in the Tracker component in DHIS2 Server allows authenticated remote attackers to execute arbitrary SQL commands via unspecified vectors. This vulnerability affects…
When was CVE-2021-39179 disclosed?
CVE-2021-39179 was first published in the National Vulnerability Database on October 29, 2021, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2021-39179 actively exploited?
CVE-2021-39179 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2% probability of exploitation in the next 30 days, which ranks it in the top 21.4% of all scored CVEs.
What is the CVSS score of CVE-2021-39179?
CVE-2021-39179 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2021-39179?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2021-39179, 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

Explore the affected products and dependency analysis for CVE-2021-39179

Explore →

Is Your Infrastructure Affected by CVE-2021-39179?

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

Start Free Scan →Browse All CVEs