CVE-2024-28247

HIGHNVD 7.67.6
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 7.6 under NVD CVSS v3. EPSS exploit probability: 1.4% (72nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated

Also known asEUVD-2024-25351 (ENISA EUVD)Source: ENISA EUVD

7.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 1.4%CVSS: 7.6Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

The Pi-hole is a DNS sinkhole that protects your devices from unwanted content without installing any client-side software. A vulnerability has been discovered in Pihole that allows an authenticated user on the platform to read internal server files arbitrarily, and because the application runs from behind, reading files is done as a privileged user.If the URL that is in the list of "Adslists" begins with "file*" it is understood that it is updating from a local file, on the other hand if it does not begin with "file*" depending on the state of the response it does one thing or another. The problem resides in the update through local files. When updating from a file which contains non-domain lines, 5 of the non-domain lines are printed on the screen, so if you provide it with any file on the server which contains non-domain lines it will print them on the screen. This vulnerability is fixed by 5.18.

CVSS v3
7.6
EG Score
7.6HIGHmedium confidence
EG Risk
50
EG Risk 50/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity76% × 45%
Impact severity (EG Severity): CVSS 7.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.4%
EPSS %ILE
72nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.6): severity, escalated by confirmed exploitation. This CVE's 7.6 is its impact severity (EG Severity), not escalated.

EG Severity
7.6 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
1.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

March 27, 2024

Last Modified

October 10, 2025

Advisory Details (2)

Auto-updated Oct 28, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Authenticated Arbitrary File Read with root privileges · Advisory · pi-hole/pi-hole · GitHub

https://github.com/pi-hole/pi-hole/security/advisories/GHSA-95g6-7q26-mp9x
GitHub commit Patch Available

commit f3af03174e67 (pi-hole/pi-hole)

Patch available: pi-hole/pi-hole v5.18 (contains commit f3af03174e67)

https://github.com/pi-hole/pi-hole/commit/f3af03174e676c20e502a92ed7842159f2fdeb7e

Weakness Classification(2)

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

Data Freshness Timeline

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

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 94 of 212 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 6 repeat rows among the latest 100 are merged into the row they repeat. The 118 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 GitHub PoC). Defenders should treat patch urgency accordingly.

  • GitHub PoCT0X1Cx/CVE-2024-28247-Pi-hole-Arbitrary-File-Read
    Published Mar 31, 2024

    This repository provides an exploit for CVE-2024-28247, highlighting a vulnerability that permits a remote attacker to read arbitrary files on the system.

    Open source ↗

Frequently asked(5)

What is CVE-2024-28247?
CVE-2024-28247 is a high-severity vulnerability; its CVE record was published on March 27, 2024. The Pi-hole is a DNS sinkhole that protects your devices from unwanted content without installing any client-side software. A vulnerability has been discovered in Pihole that allows an authenticated user on the platform to read internal server files arbitrarily, and because the application runs…
When was the CVE record for CVE-2024-28247 published?
The CVE record for CVE-2024-28247 was published on March 27, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 10, 2025; the record at its source may have been updated since.
Is CVE-2024-28247 actively exploited?
CVE-2024-28247 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.4% probability of exploitation in the next 30 days (72nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-28247?
CVE-2024-28247 has a CVSS v3 base score of 7.6 (NVD).
How do I remediate CVE-2024-28247?
A fix for CVE-2024-28247 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-28247

Explore →

Is Your Infrastructure Affected by CVE-2024-28247?

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