Filament has inconsistent scope enforcement for its AttachAction and AssociateAction Select fieldsGHSA-7q3w-xqjw-g3cr
MEDIUMGHSA-7q3w-xqjw-g3cr is a medium-severity (CVSS 6.5) CWE-639 vulnerability in filament/tables. A fix is available for filament/tables — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-7q3w-xqjw-g3cr.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-7q3w-xqjw-g3cr by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 394,803 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
filament/tables🐘filament/actions🐘filament/actionsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Filament is a collection of full-stack components for accelerated Laravel development. From filament/actions 4.0.0 until 4.11.4 and 5.6.4 and from filament/tables 3.0.0 until 3.3.51, 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. This vulnerability is fixed in filament/actions 4.11.4 and 5.6.4 and filament/tables 3.3.51.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | filament/tables | ≥ 3.0.0&&< 3.3.51 | 3.3.51composer require filament/tables:^3.3.51 |
| 🐘Packagist | filament/actions | ≥ 4.0.0&&< 4.11.4 | 4.11.4composer require filament/actions:^4.11.4 |
| 🐘Packagist | filament/actions | ≥ 5.0.0&&< 5.6.4 | 5.6.4composer require filament/actions:^5.6.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for filament/tables, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update filament/tables to 3.3.51 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7q3w-xqjw-g3cr is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is GHSA-7q3w-xqjw-g3cr in your dependencies?
Find it across Packagist, including transitive dependencies.