/

CVE-2026-33080

Severity:

HIGH RISK

(7.3)

XSS in Filament Table Summarizers (Range, Values)

CVE-2026-33080

Analyzed

Vulnerability type

Category:

Cross-Site Scripting (XSS)

CWE:

CWE-79, CWE-80

Impact:

Stored Cross-Site Scripting leading to session hijacking, data theft, and unauthorized actions in users' browsers

Severity:

HIGH RISK

(7.3)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Filament Table summarizers (Range and Values) in affected versions render raw database values without escaping HTML, allowing stored cross-site scripting (XSS) when untrusted data is displayed.

If application-level validation or sanitization is missing for columns using these summarizers, an attacker may inject malicious HTML or JavaScript that runs in the browser of any user viewing the affected tables.

Affected context

The vulnerability appears in Laravel applications using Filament versions 4.0.0–4.8.4 and 5.0.0–5.3.4 that:

  • Use Filament Tables with the Range or Values summarizers
  • Display database-backed values originating from user-controlled or otherwise untrusted sources
  • Do not perform consistent server-side validation, encoding, or sanitization for the affected columns

In these conditions, the summarizers render content back to the browser without escaping HTML, allowing injected scripts to execute in the context of the application's origin.

Exploit preconditions

  • Attack surface: Web UI displaying Filament Tables that use the Range or Values summarizers.
  • Required access: Ability to insert or influence data stored in database columns that are summarized by these components (e.g., via forms, imports, APIs, or background jobs).
  • Trigger point: A privileged or regular user loads a page containing a Filament Table where the vulnerable summarizer processes and renders the stored, malicious value.
  • Why exploitation is possible: The summarizers output raw values directly into the HTML response without escaping or encoding, violating output-encoding best practices and enabling script execution when attacker-controlled markup is present.

Why this happens

This issue stems from improper output handling in UI components that render dynamic data.

The Filament Range and Values summarizers take database values and inject them into HTML without applying context-appropriate encoding, relying implicitly on upstream validation that may not exist.

This maps to CWE-79: Improper Neutralization of Input During Web Page Generation (Cross-Site Scripting) and is closely related to CWE-80: Improper Neutralization of Script-Related HTML Tags in a Web Page, where attacker-controlled input is included as raw HTML/JavaScript in the DOM.

Conceptually, the bug class is "unescaped rendering of untrusted data," a common XSS pattern in templating and component frameworks.

Potential impact

  • Execution of arbitrary JavaScript in the victim's browser when viewing affected Filament Tables
  • Theft or misuse of session identifiers, CSRF tokens, or other sensitive browser-stored data
  • Unauthorized actions performed on behalf of logged-in users (e.g., modifying records, changing configuration)
  • Defacement or manipulation of administrative dashboards and reporting views
  • Pivoting into further attacks such as phishing overlays, keylogging, or lateral movement within the application

General mitigation guidance

Effective mitigation focuses on robust output encoding and a conservative trust model for displayed data:

  • Ensure that all Filament component outputs, especially summarizers, perform context-aware HTML encoding by default when rendering dynamic values.
  • Treat all database content as untrusted unless explicitly proven otherwise; apply output encoding even if input validation exists.
  • Implement strict server-side validation for fields shown in tables, constraining them to expected formats and rejecting or normalizing potentially dangerous markup.
  • Prefer framework helpers or templating constructs that auto-escape values rather than printing raw HTML, except in narrowly scoped, audited use cases.
  • Use content security controls (such as CSP with script-src restrictions) as a defense-in-depth measure to reduce the blast radius of any remaining XSS issues.

How teams detect issues like this

Detection typically combines code-centric and behavior-centric approaches:

  • Static analysis and code search:
  • Scan for Filament Table definitions using Range or Values summarizers where underlying columns are sourced from user input or external systems.
  • Flag any component or view logic that bypasses default escaping or uses "raw" rendering APIs in proximity to untrusted data.
  • Code review practices:
  • During reviews, verify that all table cells, summarizers, and UI widgets treat database values as untrusted and apply output encoding.
  • Look for comments or patterns indicating "HTML allowed" and ensure these cases are strictly justified and sanitized.
  • Automated testing:
  • Incorporate XSS test payloads into integration tests for administrative and reporting pages, particularly those that aggregate or summarize data.
  • Use security testing tools or browser-based scanners that can detect reflective or stored XSS on application endpoints.
  • Policy enforcement:
  • Establish internal guidelines that discourage raw HTML rendering and require justification and review for any escaping bypass.

Sources

SourceLink
github.comgithub.com/filamentphp/filament/commit/efa041aeeb4b1a99acd48aaa05584993c926d1ed
github.comgithub.com/filamentphp/filament/releases/tag/v4.8.5
github.comgithub.com/filamentphp/filament/releases/tag/v5.3.5
github.comgithub.com/filamentphp/filament/security/advisories/GHSA-vv3x-j2x5-36jc

Frequently asked

questions

Yes. If an attacker can influence data stored in the database columns displayed by the vulnerable summarizers, they can remotely inject payloads that execute when any user loads the impacted Filament Table.

Often, yes: attackers typically need some capability (authenticated or via another exposed input path) to insert or modify database records used by the Range or Values summarizers. However, this access might be indirect (e.g., via public forms or imports), depending on the application design.

Ensure that the summarizers and any similar components always perform proper HTML output encoding for rendered values and avoid raw rendering of untrusted data. Complement this with strict server-side validation to constrain stored content to safe formats.

Adopt a default-escape posture for all UI rendering, treat database content as untrusted, and enforce secure coding guidelines in reviews and CI. Automated checks for raw HTML outputs, combined with integration tests using XSS payloads, help catch regressions early.

Find out what's already
exploitable in your codebase.