CVE-2024-51758: Filament Actions Package Exposes Exported Files on Public Disk

filament/actions Updated 02 Oct 2025

Summary

07/11/2024
Yes i
Low
2.4

CVE-2024-51758: Filament has exported files stored in default (public) filesystem if not reconfigured. Affects filament/actions versions >= 3.2.0, < 3.2.123. Fixed in 3.2.123. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

Filament is a popular PHP package designed to streamline the development of admin panels and interfaces. It provides various features including file uploads, data exports, and customizable actions. The package is built to facilitate quick development, allowing users to easily switch storage drivers for production environments. However, its default configuration sets the storage disk to 'public', which can lead to security vulnerabilities if not properly reconfigured.

Vulnerability Detail

The vulnerability arises from the default configuration of the Filament Actions package, which saves exported files to a public disk. This configuration can expose sensitive data to unauthorized users, as files stored on the public disk can be accessed without proper access controls. The issue is particularly concerning for applications that do not change the default disk setting before deployment, potentially leading to data leaks and compliance violations. The vulnerability is classified under CWE-1188, indicating the risks associated with insecure default settings.

How To Fix

Minimum fixed version

3.2.123

This is the first release that contains the fix.

composer require filament/actions:3.2.123

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

If you need to continue using the public disk for exports, you can explicitly set the export disk in your configuration. Refer to the Filament documentation for instructions on customizing the storage disk for exports: https://filamentphp.com/docs/3.x/actions/prebuilt-actions/export#customizing-the-storage-disk.

Conclusion

The CVE-2024-51758 vulnerability in the Filament Actions package highlights the importance of secure default configurations in software development. By updating to the latest version and reviewing your storage settings, you can protect your application from unauthorized data access.

See every vulnerability recorded for filament/actions →

Share this vulnerability

FAQ

CVE-2024-51758 is a security vulnerability in the Filament Actions package that allows unauthorized access to exported files stored on a public disk.

You can check if your application is affected by using Vulert, which monitors open-source vulnerabilities in your software. Visit Vulert Scanner to analyze your composer.lock file without needing to sign up.

Leaving the public disk as the default can expose sensitive exported data to unauthorized users, leading to potential data breaches and compliance issues.

You can update the package by running 'composer update filament/actions' in your terminal to ensure you are using the latest version with the security fix.

If an immediate update is not possible, consider changing the default disk to 'local' or 's3' in your configuration to mitigate the risk until you can apply the update.

How To Fix

Minimum fixed version

3.2.123

This is the first release that contains the fix.

composer require filament/actions:3.2.123

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback