# CVE-2024-51758: Exported files stored in default (`public`) filesystem if not reconfigured in filament

> Attackers can access sensitive exported files stored in the public filesystem due to insecure default configuration in Filament.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 7 Nov 2024
- **Updated:** 21 Nov 2024
- **Also known as:** GHSA-4hxw-gc2q-f6f3

## What is CVE-2024-51758?

CVE-2024-51758 is a low-severity vulnerability in filamentphp filament, published on 7 Nov 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-1188 (Initialization of a Resource with an Insecure Default)

## Which versions are affected by CVE-2024-51758?

2 open source packages ship an affected version, including filament/actions.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `filament/actions` | Packagist | From 3.2.0 | 3.2.123 |
| `filament/actions` | Packagist | From 3.2.0 | 3.2.123 |

## How do I fix CVE-2024-51758?

Upgrade filament/actions to 3.2.123 or later.

## Is CVE-2024-51758 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-51758 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-51758 and fix it if it is affected.

What it is: CVE-2024-51758 is a low-severity vulnerability in filamentphp filament, published on 7 Nov 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-51758 exists.

Affected packages and fixed versions:
- filament/actions (Packagist): affected from 3.2.0; fixed in 3.2.123
- filament/actions (Packagist): affected from 3.2.0; fixed in 3.2.123

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-51758/ (Markdown: https://insights.sbomify.com/CVE-2024-51758/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-51758
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-51758
- OSV: https://osv.dev/vulnerability/CVE-2024-51758

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-51758/
Summaries are generated and may contain mistakes; the official description above is the record.