Skip to content

← Public intelligence

Packagist package

filament/actions

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 6.5PackagistPublished

    Filament has inconsistent scope enforcement for its AttachAction and AssociateAction Select fields

    CVE-2026-48067 · GHSA-7q3w-xqjw-g3cr

    Affected
    • Packagist filament/actions >= 4.0.0, <= 4.11.3; >= 5.0.0, <= 5.6.3
    Fixed in
    4.11.45.6.4· Vendor fix available
    Issue
    The recordSelectOptionsQuery() method may be used to scope the options available in the Select field for AttachAction and AssociateAction. However, the built-in validation rule for these fields did not apply the same scope. As a result, a user who can trigger these actions could tamper with the Livewire component's state and submit an out-of-scope value.

    Recommended action: Upgrade to 5.6.4 or 4.11.4 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Low, CVSS 2.3PackagistPublished

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

    CVE-2024-51758 · GHSA-4hxw-gc2q-f6f3

    Affected
    • Packagist filament/actions >= 3.2.0, < 3.2.123
    Fixed in
    3.2.123· Vendor fix available
    Issue
    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…

    Recommended action: Upgrade to 3.2.123 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →