CVE-2024-51758

LOWNVD 2.32.3—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 2.3 under NVD CVSS v3. EPSS exploit probability: 0.6% (44th percentile of EPSS-scored CVEs). 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
2.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 2.3Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Filament is a collection of full-stack components for accelerated Laravel development. All Filament features that interact with storage use the default_filesystem_disk config option. This allows the user to easily swap their storage driver to something production-ready like s3 when deploying their app, without having to touch multiple configuration options and potentially forgetting about some. The default disk is set to public when you first install Filament, since this allows users to quickly get started developing with a functional disk that allows features such as file upload previews locally without the need to set up an S3 disk with temporary URL support. However, some features of Filament such as exports also rely on storage, and the files that are stored contain data that should often not be public. This is not an issue for the many deployed applications, since many use a secure default disk such as S3 in production. However, CWE-1188 suggests that having the public disk as the default disk in Filament is a security vulnerability itself. As such, we have implemented a measure to protect users whereby if the public disk is set as the default disk, the exports feature will automatically swap it out for the local disk, if that exists. Users who set the default disk to local or s3 already are not affected. If a user wants to continue to use the public disk for exports, they can by setting the export disk deliberately. This change has been included in the 3.2.123 release and all users who use the public disk are advised to upgrade.

CVSS v3
2.3
EG Score
2.3LOWmedium confidence
EG Risk
26
EG Risk 26/100CISA SSVC

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
Severity23% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.6%
EPSS %ILE
45th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

November 7, 2024

Last Modified

April 15, 2026

References (2)

Vendor Advisories for CVE-2024-51758(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFix by version rangeDependents
filament/actionsv3.2.0 ... v3.2.99 (125 versions)
  • 3.2.0 up to 3.2.123: fixed in 3.2.123
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 34× 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 199 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Same product

1 shown

Packagist:filament/actions

Frequently asked(5)

What is CVE-2024-51758?
CVE-2024-51758 is a low vulnerability published on November 7, 2024. Filament is a collection of full-stack components for accelerated Laravel development. All Filament features that interact with storage use the defaultfilesystemdisk config option. This allows the user to easily swap their storage driver to something production-ready like s3 when deploying their…
When was CVE-2024-51758 disclosed?
CVE-2024-51758 was first published on November 7, 2024, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-51758 actively exploited?
CVE-2024-51758 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-51758?
CVE-2024-51758 has a CVSS v3 base score of 2.3 (NVD).
How do I remediate CVE-2024-51758?
A fix for CVE-2024-51758 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-51758 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-51758

Explore →

Is Your Infrastructure Affected by CVE-2024-51758?

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

Book a Demo →Browse All CVEs