Low severity · published Nov 7, 2024
CVE-2024-51758
Exported files stored in default (`public`) filesystem if not reconfigured in filament
2.3
CVSS
0.6%
EPSS
No
On KEV
Description
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](https://cwe.mitre.org/data/definitions/1188.html) 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.
Exploitation
Is it being used?
Exploit prediction (EPSS)0.6% · higher than 47% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
FI
filament · filamentphp
>= 3.2.0, < 3.2.123 · source: vendor
EE
Excel Export · Filament
through 3.2.0; before 3.2.123 · source: CISA
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2024-51758
CVE.org
https://www.cve.org/CVERecord?id=CVE-2024-51758
filamentphp.com
https://filamentphp.com/docs/3.x/actions/prebuilt-actions/export#customizing-the-storage-disk
github.com
https://github.com/filamentphp/filament/security/advisories/GHSA-4hxw-gc2q-f6f3
More from filament
8.1
CVE-2026-77567
Filament: App-based MFA can be bypassed when recovery codes are enabled
8.1
CVE-2025-67507
Filament's multi-factor authentication (app) recovery codes can be used multiple times
7.6
CVE-2026-55409
Filament: Disabled RichEditor field state can be used for XSS
7.4
CVE-2026-48505
Filament: Multi-factor authentication (app) recovery codes can still be used multiple times via concurrent submission
6.5
CVE-2026-84306
Filament: Multi-factor authentication (app) codes can still be used after a newer code has been used
