# CVE-2026-48167: Filament: Unvalidated ImageColumn and ImageEntry values can be used for XSS

> Attackers can inject malicious scripts via unvalidated image values in Filament components, leading to stored XSS for users viewing tables or schemas.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Jun 2026
- **Updated:** 23 Jun 2026
- **Also known as:** GHSA-3fc8-8hp6-6jr4

## What is CVE-2026-48167?

CVE-2026-48167 is a medium-severity cross-site scripting vulnerability in filamentphp filament, published on 22 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-48167?

8 open source packages ship an affected version, including filament/infolists and filament/tables.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `filament/infolists` | Packagist | From 4.0.0 | 4.11.5 |
| `filament/infolists` | Packagist | From 4.0.0 | 4.11.5 |
| `filament/infolists` | Packagist | From 5.0.0 | 5.6.5 |
| `filament/infolists` | Packagist | From 5.0.0 | 5.6.5 |
| `filament/tables` | Packagist | From 4.0.0 | 4.11.5 |
| `filament/tables` | Packagist | From 4.0.0 | 4.11.5 |
| `filament/tables` | Packagist | From 5.0.0 | 5.6.5 |
| `filament/tables` | Packagist | From 5.0.0 | 5.6.5 |

## How do I fix CVE-2026-48167?

Upgrade filament/infolists to a fixed version for your release line: 4.11.5 or 5.6.5.

## Is CVE-2026-48167 being exploited?

There is no known exploitation of CVE-2026-48167 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48167 and fix it if it is affected.

What it is: CVE-2026-48167 is a medium-severity cross-site scripting vulnerability in filamentphp filament, published on 22 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-48167 in the wild and no public exploit code.

Affected packages and fixed versions:
- filament/infolists (Packagist): affected from 4.0.0; fixed in 4.11.5
- filament/infolists (Packagist): affected from 4.0.0; fixed in 4.11.5
- filament/infolists (Packagist): affected from 5.0.0; fixed in 5.6.5
- filament/infolists (Packagist): affected from 5.0.0; fixed in 5.6.5
- filament/tables (Packagist): affected from 4.0.0; fixed in 4.11.5
- filament/tables (Packagist): affected from 4.0.0; fixed in 4.11.5
- filament/tables (Packagist): affected from 5.0.0; fixed in 5.6.5
- filament/tables (Packagist): affected from 5.0.0; fixed in 5.6.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-48167/ (Markdown: https://insights.sbomify.com/CVE-2026-48167/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48167
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48167
- OSV: https://osv.dev/vulnerability/CVE-2026-48167

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-48167/
Summaries are generated and may contain mistakes; the official description above is the record.