CVE-2026-48167: Stored XSS in Filament ImageColumn & ImageEntry Components

Technical summary

The ImageColumn and ImageEntry components in Filament versions 4.0.0 through 4.11.4 and 5.0.0 through 5.6.4 fail to escape HTML content when rendering image data retrieved from the database. The vulnerability maps to CWE-79 (Improper Neutralization of Input During Web Page Generation). An attacker who can insert or modify image-related database records can craft payloads that execute JavaScript in the browsers of administrators, staff, or other users who view the compromised table or admin panel. The attack requires prior authentication (the CVSS vector reflects PR:L—low privilege required) and does not require user interaction at the point of view (UI:N), making it straightforward to exploit once database access is achieved.

Business impact

Stored XSS in an admin panel or dashboard framework poses significant operational and compliance risk. An attacker with low-privilege database access can escalate impact by harvesting session tokens, modifying admin settings, or defacing data visible to high-privilege users. In regulated environments, this vulnerability may trigger incident notification obligations. Teams relying on Filament for admin interfaces should assess whether image metadata is user-controllable and whether their current input validation is sufficient to prevent injection.

Affected systems

Filament versions 4.0.0 through 4.11.4 and versions 5.0.0 through 5.6.4 are vulnerable. Versions 4.11.5 and 5.6.5 and later contain the fix. Applications using Filament must verify their installed version and confirm whether ImageColumn or ImageEntry components are used with data sources that may be user-influenced (e.g., image ALT text, titles, or file paths stored in user-submitted forms).

Exploitability

The vulnerability requires an authenticated attacker with sufficient application privileges to insert or modify image-related data in the database. It does not require tricking users into clicking links or performing additional actions—the payload executes automatically when the affected page loads. In environments where multiple users access the same admin panel, a single compromised or malicious low-privilege account can affect high-privilege users, making this a privilege-escalation vector. Public exploit code has not been disclosed, but the fix is straightforward and the attack surface is clear.

Remediation

Update Filament to version 4.11.5 or later (for the 4.x line) or version 5.6.5 or later (for the 5.x line). Vendors should communicate patch availability and timelines in accordance with their support policy. As an interim control, validate and sanitize all user-supplied data before storing it in fields associated with ImageColumn or ImageEntry components. Consider implementing Content Security Policy (CSP) headers to reduce the blast radius of any stored XSS.

Patch guidance

Apply the latest available patch from the Filament maintainers. For version 4.x, upgrade to 4.11.5 or newer. For version 5.x, upgrade to 5.6.5 or newer. Test patched versions in a staging environment to ensure compatibility with your application and any custom extensions or configurations. If you maintain internal or custom Filament installations, verify against the vendor advisory that your patched version includes the HTML escaping fix for ImageColumn and ImageEntry.

Detection guidance

Review your Filament installation version against the affected range (4.0.0–4.11.4 and 5.0.0–5.6.4). Audit database schemas and application code to identify where ImageColumn and ImageEntry are used and whether the source data is user-controllable. Monitor application logs for unusual image metadata submissions or suspicious HTML/JavaScript patterns in image fields. Web Application Firewalls (WAF) may flag stored payloads if they pattern-match common XSS signatures, though they cannot prevent database-level attacks. Consider scanning image metadata and ALT text fields for script tags or event handlers.

Why prioritize this

This vulnerability merits prompt patching because it affects a widely-used Laravel framework, targets admin interfaces (where high-privilege users operate), and enables stored XSS with no user interaction required at exploitation. While the CVSS score is MEDIUM (6.4), the practical impact could be significant if your application's image metadata is user-controllable or if your admin user base includes sensitive roles. Prioritize patching if your Filament deployment exposes image data that end users or semi-trusted staff can influence.

Risk score, explained

The CVSS v3.1 score of 6.4 (MEDIUM) reflects a network-accessible vulnerability requiring low privileges and no user interaction, but with limited scope containment and confidentiality/integrity impact (no availability impact). The score does not account for context-specific factors: stored XSS in admin panels often carries higher risk than reflected XSS because the payload persists and reaches high-privilege users automatically. Organizations should consider their specific threat model and user roles when deciding priority.

Frequently asked questions