CVE-2026-48167: filamentphp filament · Cross-site Scripting
Affects filamentphp filamentSource CVE Database V5
Not known to be exploited · CVSS 6.4 Medium : upgrade to 5.6.5 or 4.11.5 when convenient.
Data as of 5 Nov 2026, 00:01 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.6.5, 4.11.5
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 22 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
Upgrade filament and filamentphp/filament to 5.6.5 or 4.11.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| filamentphpfilament | Affected
| Fixed in
|
| filamentphpfilament | Affected
| Fixed in
|
Packagistfilamentphp/filamentpkg:composer/filamentphp/filamentOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in filament versions 4.11.5 and 5.6.5. Users should upgrade to these or later versions to remediate the vulnerability. Until upgraded, ensure that any data passed to ImageColumn and ImageEntry components is properly validated and sanitized to prevent injection of malicious HTML or JavaScript.
Description
Filament is a collection of full-stack components for accelerated Laravel development. From 4.0.0 until 4.11.5 and 5.6.5, 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. This vulnerability is fixed in 4.11.5 and 5.6.5.