CVE Tools
Track your stack

CVE-2024-51758

Exported files stored in default (`public`) filesystem if not reconfigured in filament

No known exploitation. EPSS puts it in the 46th percentile. Fixed in 3.2.123.

CVSS 3.13.4LowEPSS percentile46th0.6% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
No public exploit knownFix3.2.123Upgrade to this build

Published Updated Sources: CVE.org, NVD, GitHub, BDU

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

  • Filamentphp FilamentAffected: >= 3.2.0, < 3.2.123Upgrade to: not statedStated by: CVE record
  • Packagist filament/actionsAffected: ≥ 3.2.0, < 3.2.123Upgrade to: 3.2.123Stated by: GitHub advisory
  • Сообщество свободного программного обеспечения FilamentAffected: до 3.2.123Upgrade to: not statedStated by: BDU

Versions as the sources state them. Full version matrix after sign-in

What it is

From the CVE record

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.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS46th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.6% chance of exploitation activity in the next 30 days, which ranks it in the 46th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

4 events over 14 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. Publishedweakness classified

Affected products

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:N/A:N

Scored 3.4 by bdu.

How it is reached

  • Access Vector NetworkExploitable remotely over the network
  • Access Complexity HighSpecialized conditions required

Impact if exploited

  • Confidentiality L
  • Integrity NoneNo integrity impact
  • Availability NoneNo availability impact

Weaknesses

Sources

References in the record

And 5 more references. See all after sign-in

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Filament/actions, not every advisory.