Filament has exported files stored in default (public) filesystem if not reconfigured

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

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 · score source

EPSS

• CVE-2024-51758: 0.56% estimated exploitation activity in the next 30 days; percentile 46.93 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 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: Developers often choose…

Published by the source

7 Nov 2024, 16:14 UTC

Last modified by the source

8 Jun 2026, 20:07 UTC

Source last checked

26 Oct 2026, 14:48 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-4hxw-gc2q-f6f3

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-51758

Advisory: Filament has exported files stored in default (`public`) filesystem if not reconfigured
IDs: CVE-2024-51758, GHSA-4hxw-gc2q-f6f3
Record: https://patchnext.com/advisories/cve-2024-51758 (revision 1, source checked 26 Oct 2026, 14:48 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: filament/actions 3.2.123. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist filament/actions: affected >= 3.2.0, < 3.2.123; fixed in 3.2.123

## Suggested inspection (read-only)
- Packagist filament/actions: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on filament/actions.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-4hxw-gc2q-f6f3 (GitHub-reviewed advisory GHSA-4hxw-gc2q-f6f3 lists affected ranges: Packagist filament/actions >=3.2.0 <3.2.123)

Commands are suggestions: review each one before running it.