cve.bz

CVE-2026-48167 filamentphp filament: Cross-site Scripting

6.4 mediumEPSS 0.2%Fix available

Medium (6.4) in filamentphp filament. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in filament/infolists 4.11.5, 5.6.5.

On this page
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.

Severity

CVSS 3.1

6.4 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 16th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-06-23. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-79 Improper Neutralization of Input During Web Page Generation (Cross-site Scripting)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • filament/infolists (Packagist): fixed in 4.11.5, 5.6.5
  • filament/tables (Packagist): fixed in 4.11.5, 5.6.5

Ask an AI about this CVE

Show the promptExplain CVE-2026-48167 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-48167?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-48167?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-48167 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
filamentphp filament>= 4.0.0, < 4.11.5
filamentphp filament>= 5.0.0, < 5.6.5

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-3fc8-8hp6-6jr4Packagistfilament/infolists>=4.0.0 <4.11.54.11.5
GHSA-3fc8-8hp6-6jr4Packagistfilament/tables>=4.0.0 <4.11.54.11.5
GHSA-3fc8-8hp6-6jr4Packagistfilament/infolists>=5.0.0 <5.6.55.6.5
GHSA-3fc8-8hp6-6jr4Packagistfilament/tables>=5.0.0 <5.6.55.6.5

Attack patterns (CAPEC)

  • CAPEC-63 Cross-Site Scripting (XSS) Likelihood: High · Severity: Very High
  • CAPEC-85 AJAX Footprinting Likelihood: High · Severity: Low
  • CAPEC-209 XSS Using MIME Type Mismatch Severity: Medium
  • CAPEC-588 DOM-Based XSS Likelihood: High · Severity: Very High
  • CAPEC-591 Reflected XSS Likelihood: High · Severity: Very High
  • CAPEC-592 Stored XSS Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON