dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-48167

MEDIUM · 6.4 CVSS v3.1 Published 2026-06-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Filament's ImageColumn and ImageEntry components (versions 4.0.0-4.11.4 and 5.6.4) fail to escape HTML when rendering database values, allowing stored XSS via malicious image URLs or metadata containing HTML/JavaScript that executes when users view affected tables or resource schemas.

MitigationUpgrade Filament to version 4.11.5 or 5.6.5 or later. Additionally, audit existing database records for image columns to detect and remediate any previously injected malicious payloads.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Filament version
    Run 'composer show filament/filament' or check your composer.json to see the exact version installed
    Affected if The version is 4.0.0-4.11.4 or 5.6.4 exactly (not 4.11.5+ or 5.6.5+)
  2. Identify ImageColumn usage
    Search your codebase for 'ImageColumn::make' in resource files under the Filament resources directory
    Affected if ImageColumn is used in any Filament resource to display image data from the database
  3. Identify ImageEntry usage
    Search your codebase for 'ImageEntry::make' in resource files, particularly in relation to Infolists
    Affected if ImageEntry is used in any Filament infolist to render image data from the database
  4. Inspect database for unsanitized content
    Query your database tables that use ImageColumn or ImageEntry: SELECT column_name FROM table_name WHERE column_name LIKE '%<%' OR column_name LIKE '%javascript:%'
    Affected if Any records contain raw HTML tags, script tags, or javascript: URIs in the image column fields

You are affected if you use Filament versions 4.0.0-4.11.4 or 5.6.4 AND use ImageColumn or ImageEntry components to display database values, particularly if your database may contain unsanitized image URLs or metadata.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Filament to version 4.11.5 or 5.6.5 or later. Additionally, audit existing database records for image columns to detect and remediate any previously injected malicious payloads.

Recommended fix High confidence

Filament 4.11.5 or 5.6.5 (depending on your current major version branch)

  1. 1. Identify which Filament version branch (4.x or 5.x) your Laravel project is currently using
  2. 2. For Filament 4.x users: Run `composer require filament/filament:^4.11.5` to upgrade to the fixed version
  3. 3. For Filament 5.x users: Run `composer require filament/filament:^5.6.5` to upgrade to the fixed version
  4. 4. Run `composer update` to apply the changes
  5. 5. Test your application to ensure the ImageColumn and ImageEntry components function correctly after the upgrade
  6. 6. Verify that any custom ImageColumn or ImageEntry implementations properly escape HTML if you have overridden default rendering
Caveat Review Filament's changelog between your current version and the target version for any breaking changes, though this is a security patch release likely containing minimal changes

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-48167 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-48167 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data