Filament: Inconsistent scope enforcement for AttachAction and AssociateAction Select fields
filamentphp filament
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| filament/tables Packagist |
|
|
| filament/actions Packagist |
|
|
filamentphp filament
| Product | Affected | Fixed in |
|---|---|---|
| filament/tables Packagist |
|
|
| filament/actions Packagist |
|
|
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.
From the CVE record · GitHub_M
The built-in validation for AttachAction and AssociateAction Select fields does not enforce the scope set by recordSelectOptionsQuery(). A user who can trigger these actions can tamper with the Livewire component state and submit an out-of-scope value.
Check applications using filament/tables >=3.0.0 and <3.3.51, filament/actions >=4.0.0 and <4.11.4, or filament/actions >=5.0.0 and <5.6.4.