CVE-2024-31218

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.7% (53rd 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

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

9.8EG
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).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Webhood is a self-hosted URL scanner used analyzing phishing and malicious sites. Webhood's backend container images in versions 0.9.0 and earlier are subject to Missing Authentication for Critical Function vulnerability. This vulnerability allows an unauthenticated attacker to send a HTTP request to the database (Pocketbase) admin API to create an admin account. The Pocketbase admin API does not check for authentication/authorization when creating an admin account when no admin accounts have been added. In its default deployment, Webhood does not create a database admin account. Therefore, unless users have manually created an admin account in the database, an admin account will not exist in the deployment and the deployment is vulnerable. Versions starting from 0.9.1 are patched. The patch creates a randomly generated admin account if admin accounts have not already been created i.e. the vulnerability is exploitable in the deployment. As a workaround, users can disable access to URL path starting with /api/admins entirely. With this workaround, the vulnerability is not exploitable via network.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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
0.7%
EPSS %ILE
53rd
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). 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 or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days 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 or medium mission impact; Attend at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable yes (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)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

April 5, 2024

Last Modified

April 15, 2026

Advisory Details (2)

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

Missing Authentication for Critical Function in Webhood backend · Advisory · webhood-io/webhood · GitHub

https://github.com/webhood-io/webhood/security/advisories/GHSA-h533-rxhm-73j2
GitHub commit Patch Available

commit 735e7fa2814e (webhood-io/webhood)

Patch available: webhood-io/webhood v0.9.1 (contains commit 735e7fa2814e)

https://github.com/webhood-io/webhood/commit/735e7fa2814edeec9a2c07778ed51b3c018609f9

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 53× 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 95 of 255 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. 5 repeat rows among the latest 100 are merged into the row they repeat. The 160 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 0.7% · 53rd percentile
  2. 2026-11-02 13:49 UTCEG score recompute
  3. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  4. 2026-11-01 13:10 UTCEG score recompute
  5. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  6. 2026-10-31 12:28 UTCEG score recompute
  7. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  8. 2026-10-30 11:49 UTCEG score recompute
  9. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  10. 2026-10-29 11:10 UTCEG score recompute
  11. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  12. 2026-10-28 10:26 UTCEG score recompute
  13. 2026-10-27 16:29 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  14. 2026-10-27 08:55 UTCEG score recompute
  15. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  16. 2026-10-25 17:12 UTCEG score recompute
  17. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  18. 2026-10-25 06:01 UTCEG score recompute
  19. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  20. 2026-10-24 05:22 UTCEG score recompute
  21. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  22. 2026-10-23 04:43 UTCEG score recompute
  23. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  24. 2026-10-22 04:03 UTCEG score recompute
  25. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
Show 70 more
  1. 2026-10-21 03:23 UTCEG score recompute
  2. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  3. 2026-10-20 02:44 UTCEG score recompute
  4. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  5. 2026-10-19 02:05 UTCEG score recompute
  6. 2026-10-18 07:18 UTCEG score recompute
  7. 2026-10-18 01:23 UTCEG score recompute
  8. 2026-10-17 16:30 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  9. 2026-10-17 00:42 UTCEG score recompute
  10. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  11. 2026-10-16 00:01 UTCEG score recompute
  12. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  13. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  14. 2026-10-14 16:02 UTCEG score recompute
  15. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  16. 2026-10-12 17:56 UTCEG score recompute
  17. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  18. 2026-10-11 21:20 UTCEG score recompute
  19. 2026-10-11 16:14 UTCEG score recompute
  20. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  21. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  22. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  23. 2026-10-08 17:07 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  24. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  25. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  26. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  27. 2026-10-05 00:15 UTCOSV refresh
  28. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  29. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  30. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  31. 2026-09-30 19:42 UTCEG score recompute
  32. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  33. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  34. 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  35. 2026-09-27 13:43 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  36. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  37. 2026-09-26 00:23 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  38. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  39. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  40. 2026-09-22 14:46 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  41. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  42. 2026-09-19 15:40 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  43. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  44. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  45. 2026-09-15 08:54 UTCOSV refresh
  46. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  47. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  48. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  49. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  50. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  51. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  52. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  53. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  54. 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  55. 2026-09-04 13:58 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  56. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  57. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  58. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  59. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  60. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  61. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  62. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  63. 2026-08-27 08:04 UTCOSV refresh
  64. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  65. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  66. 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  67. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  68. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  69. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  70. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.7% · 50th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-31218?
CVE-2024-31218 is a critical-severity vulnerability; its CVE record was published on April 5, 2024. Webhood is a self-hosted URL scanner used analyzing phishing and malicious sites. Webhood's backend container images in versions 0.9.0 and earlier are subject to Missing Authentication for Critical Function vulnerability. This vulnerability allows an unauthenticated attacker to send a HTTP request…
When was the CVE record for CVE-2024-31218 published?
The CVE record for CVE-2024-31218 was published on April 5, 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 April 15, 2026; the record at its source may have been updated since.
Is CVE-2024-31218 actively exploited?
CVE-2024-31218 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-31218?
CVE-2024-31218 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2024-31218?
A fix for CVE-2024-31218 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-31218

Explore →

Is Your Infrastructure Affected by CVE-2024-31218?

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

Book a Demo →Browse All CVEs