CVE-2020-11108

CRITICALNVD 8.89.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 78% probability of exploitation within the next 30 days (top 0.5% of all CVEs). NVD baseline CVSS 8.8 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Weaponized
9.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 78%
  • Public exploit code is available (Metasploit, Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 78%CVSS: 8.8Exploit: Metasploit · Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed: 0

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

The Gravity updater in Pi-hole through 4.4 allows an authenticated adversary to upload arbitrary files. This can be abused for Remote Code Execution by writing to a PHP file in the web directory. (Also, it can be used in conjunction with the sudo rule for the www-data user to escalate privileges to root.) The code error is in gravity_DownloadBlocklistFromUrl in gravity.sh.

CVSS v3
8.8
EG Score
9.0(high)
EG Risk
76(Track)
EG Risk 76/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
Severity90% × 45%
Exploitation78% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
78%
EPSS %ILE
100%
KEV
Not listed

Published

May 11, 2020

Last Modified

November 21, 2024

Advisory Details (3)

Auto-updated Aug 17, 2026
No patch confirmed yet.
generic

Packet Storm Security

http://packetstormsecurity.com/files/157748/Pi-Hole-heisenbergCompensator-Blocklist-OS-Command-Execution.html
generic

GitHub - Frichetten/CVE-2020-11108-PoC: PoCs for CVE-2020-11108; an RCE and priv esc in Pi-hole · GitHub

https://github.com/Frichetten/CVE-2020-11108-PoC
generic

CVE-2020-11108: How I Stumbled into a Pi-hole RCE+LPE

https://frichetten.com/blog/cve-2020-11108-pihole-rce/

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 15× 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.

  1. 2026-09-18 19:23 UTCEPSS rescore
  2. 2026-09-17 19:22 UTCEPSS rescore
  3. 2026-09-16 14:04 UTCEPSS rescore
  4. 2026-09-16 14:04 UTCEPSS rescore
  5. 2026-09-13 16:42 UTCEPSS rescore
  6. 2026-09-12 14:56 UTCEPSS rescore
  7. 2026-09-07 12:48 UTCOSV refresh
  8. 2026-09-06 13:44 UTCEPSS rescore
  9. 2026-09-05 15:24 UTCEPSS rescore
  10. 2026-09-02 14:08 UTCEPSS rescore
  11. 2026-09-01 03:32 UTCEPSS rescore
  12. 2026-08-30 19:14 UTCEPSS rescore
  13. 2026-08-28 21:37 UTCEPSS rescore
  14. 2026-08-26 14:42 UTCEPSS rescore
  15. 2026-08-25 13:45 UTCEPSS rescore
  16. 2026-08-20 21:31 UTCOSV refresh
  17. 2026-08-19 17:00 UTCEPSS rescore
  18. 2026-08-16 14:52 UTCEPSS rescore
  19. 2026-08-16 02:11 UTCEPSS rescore
  20. 2026-08-15 01:26 UTCEPSS rescore
  21. 2026-08-13 21:57 UTCEPSS rescore
  22. 2026-08-12 13:47 UTCEPSS rescore
  23. 2026-08-06 13:43 UTCEPSS rescore
  24. 2026-08-05 13:41 UTCOSV refresh
  25. 2026-08-04 10:34 UTCEPSS rescore
Show 57 more
  1. 2026-07-30 16:24 UTCEPSS rescore
  2. 2026-07-26 14:51 UTCEPSS rescore
  3. 2026-07-25 14:14 UTCEPSS rescore
  4. 2026-07-24 14:14 UTCEPSS rescore
  5. 2026-07-23 14:15 UTCEPSS rescore
  6. 2026-07-23 14:15 UTCEPSS rescore
  7. 2026-07-23 01:48 UTCEG score recompute▲ 0.20
  8. 2026-07-22 22:32 UTCEG score recompute▼ 0.20
  9. 2026-07-22 14:05 UTCEPSS rescore
  10. 2026-07-21 15:22 UTCEPSS rescore
  11. 2026-07-21 15:22 UTCEPSS rescore
  12. 2026-07-19 12:54 UTCOSV refresh
  13. 2026-07-16 16:59 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-11 08:24 UTCEPSS rescore
  18. 2026-07-07 13:43 UTCEPSS rescore
  19. 2026-07-01 22:01 UTCOSV refresh
  20. 2026-07-01 15:03 UTCEPSS rescore
  21. 2026-07-01 15:03 UTCEPSS rescore
  22. 2026-06-27 03:06 UTCEPSS rescore
  23. 2026-06-25 13:47 UTCEPSS rescore
  24. 2026-06-25 13:47 UTCEPSS rescore
  25. 2026-06-23 21:31 UTCEPSS rescore
  26. 2026-06-23 21:31 UTCEPSS rescore
  27. 2026-06-17 17:50 UTCEPSS rescore
  28. 2026-06-17 17:50 UTCEPSS rescore
  29. 2026-06-16 17:50 UTCEPSS rescore
  30. 2026-06-16 17:50 UTCEPSS rescore
  31. 2026-06-15 17:46 UTCEPSS rescore
  32. 2026-06-14 23:15 UTCEPSS rescore
  33. 2026-06-14 23:15 UTCEPSS rescore
  34. 2026-06-14 03:13 UTCOSV refresh
  35. 2026-06-13 22:58 UTCEPSS rescore
  36. 2026-06-13 22:58 UTCEPSS rescore
  37. 2026-06-10 22:16 UTCEPSS rescore
  38. 2026-06-10 22:16 UTCEPSS rescore
  39. 2026-06-10 13:20 UTCEPSS rescore
  40. 2026-06-07 15:23 UTCEPSS rescore
  41. 2026-06-07 15:23 UTCEPSS rescore
  42. 2026-06-06 13:45 UTCEPSS rescore
  43. 2026-06-06 13:45 UTCEPSS rescore
  44. 2026-06-06 13:45 UTCEPSS rescore
  45. 2026-06-05 22:45 UTCEPSS rescore
  46. 2026-06-05 22:45 UTCEPSS rescore
  47. 2026-06-05 06:08 UTCEPSS rescore
  48. 2026-06-04 13:10 UTCEPSS rescore
  49. 2026-06-04 13:10 UTCEPSS rescore
  50. 2026-06-01 13:50 UTCEPSS rescore
  51. 2026-05-28 13:43 UTCEPSS rescore
  52. 2026-05-28 13:43 UTCEPSS rescore
  53. 2026-05-27 03:45 UTCEG score recompute
  54. 2026-05-27 03:45 UTCGHSA enrichment
  55. 2026-05-26 13:42 UTCEPSS rescore
  56. 2026-05-26 13:42 UTCEPSS rescore
  57. 2026-05-26 06:46 UTCOSV refresh

Publicly available exploits

(6 references)

Working exploit code is in the public domain (1 Metasploit module) (1 GitHub PoC) (4 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-48519✓ verified
    First seen May 26, 2020

    Pi-hole 4.4.0 - Remote Code Execution (Authenticated)

    Open source ↗
  • Exploit-DBEDB-48491✓ verified
    First seen May 19, 2020

    Pi-Hole - heisenbergCompensator Blocklist OS Command Execution (Metasploit)

    Open source ↗
  • Exploit-DBEDB-48442
    First seen May 10, 2020

    Pi-hole < 4.4 - Authenticated Remote Code Execution

    Open source ↗
  • Exploit-DBEDB-48443
    First seen May 10, 2020

    Pi-hole < 4.4 - Authenticated Remote Code Execution / Privileges Escalation

    Open source ↗
  • Metasploitexploit/unix/http/pihole_blocklist_exec✓ verified
    First seen May 10, 2020

    Pi-Hole heisenbergCompensator Blocklist OS Command Execution

    Open source ↗
  • GitHub PoCFrichetten/CVE-2020-11108-PoC
    First seen Apr 4, 2020

    PoCs for CVE-2020-11108; an RCE and priv esc in Pi-hole

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2020-11108?
CVE-2020-11108 is a critical vulnerability published on May 11, 2020. The Gravity updater in Pi-hole through 4.4 allows an authenticated adversary to upload arbitrary files. This can be abused for Remote Code Execution by writing to a PHP file in the web directory. (Also, it can be used in conjunction with the sudo rule for the www-data user to escalate privileges to…
When was CVE-2020-11108 disclosed?
CVE-2020-11108 was first published in the National Vulnerability Database on May 11, 2020, 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-2020-11108 actively exploited?
CVE-2020-11108 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 78% probability of exploitation in the next 30 days, which ranks it in the top 0.4% of all scored CVEs.
What is the CVSS score of CVE-2020-11108?
CVE-2020-11108 has a CVSS v3 base score of 8.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2020-11108?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-11108, 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-2020-11108

Explore →

Is Your Infrastructure Affected by CVE-2020-11108?

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

Start Free Scan →Browse All CVEs