Filament: Unvalidated ImageColumn and ImageEntry values can be used for XSS
Published 23 Jun 2026 · Updated 10 Sept 2026
Is your project on an affected filament/infolists?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=4.0.0 <4.11.5
- Fixed in
- 4.11.5
composer require filament/infolists:^4.11.5- Affected
- >=4.0.0 <4.11.5
- Fixed in
- 4.11.5
composer require filament/tables:^4.11.5- Affected
- >=5.0.0 <5.6.5
- Fixed in
- 5.6.5
composer require filament/infolists:^5.6.5- Affected
- >=5.0.0 <5.6.5
- Fixed in
- 5.6.5
composer require filament/tables:^5.6.5Details
The ImageColumn and ImageEntry components render raw database values without escaping HTML. Where the data passed to these components isn't validated, an attacker could plant malicious HTML or JavaScript and achieve stored XSS that executes for users who view the table or schema.
Is GHSA-3fc8-8hp6-6jr4 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected filament/infolists, and gives you the command that fixes it.
More advisories for filament/infolists
- MediumCVE-2024-47186Filament has unvalidated ColorColumn and ColorEntry values that can be used for Cross-site Scripting · 27 Sept 2024
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.