Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:NSummary
CVE-2026-33080 is a high-severity Cross-site Scripting (CWE-79) vulnerability in Filamentphp Filament. Its CVSS base score is 7.3 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Browser Session Hijacking (T1185); ranked at the 22th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-33080 is a stored cross-site scripting (XSS) vulnerability (CWE-79, CWE-80) in Filament, a collection of full-stack components for accelerated Laravel development. The issue affects the Range and Values table summarizers in versions 4.0.0 through 4.8.4 and 5.0.0 through 5.3.4, which render raw database values without escaping HTML. This flaw arises when there is insufficient validation of data in columns using these summarizers, allowing malicious HTML or JavaScript to be stored and rendered. The vulnerability has a CVSS v3.1 base score of 7.3 (AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N).
An attacker with low privileges, such as an authenticated user able to insert data into affected table columns, can exploit this by planting malicious payloads in the database. When administrators or other users view the table with the vulnerable summarizers enabled, the payload executes in their browsers, leading to stored XSS. Successful exploitation enables high-impact confidentiality and integrity violations, such as session hijacking, data theft, or unauthorized actions on behalf of the victim, though it requires user interaction and does not affect availability.
The Filament security advisory (GHSA-vv3x-j2x5-36jc) and related GitHub references confirm the issue has been addressed in versions 4.8.5 and 5.3.5 via a specific commit (efa041aeeb4b1a99acd48aaa05584993c926d1ed) that implements proper HTML escaping. Security practitioners should upgrade to these patched versions immediately and review custom table implementations for adequate input validation on summarizer columns to mitigate risks in unpatched environments.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-13647
Vulnerability Data
Filament is a collection of full-stack components for accelerated Laravel development. Versions 4.0.0 through 4.8.4 and 5.0.0 through 5.3.4 have two Filament Table summarizers (Range, Values) that render raw database values without escaping HTML. If there is a lack of…
more
validation for the data in the columns that use these summarizers, an attacker could plant malicious HTML / JavaScript and achieve stored XSS that executes for users who view the table with those summarizers. This issue has been patched in versions 4.8.5 and 5.3.5.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.1.2V1.3.2V1.2.1V1.3.1
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover missing or incorrect input neutralization through targeted web-application tests.
Input validation directly enforces neutralization of untrusted data before it reaches web output generation.
Output filtering can catch or sanitize unneutralized script content before it is served to users.
Secure engineering principles include mandatory output encoding and neutralization of HTML metacharacters to stop injection at the source.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly target introduction of XSS via coding standards/testing (mostly), yet the single broad outcome leaves many specific neutralization vectors unaddressed (partial).
Patching and EOL replacement can remediate known XSS instances in libraries or frameworks (partial) but do nothing to enforce input neutralization in application code (none).
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure-coding testing and automated code-analysis tools are applied to detect improper neutralization of script-related content during web-page generation.
Knowledge exchange on emerging attack techniques and patches reduces the likelihood that cross-site scripting flaws remain unaddressed in deployed applications.
Operational indicators of compromise for web-application attacks can be incorporated into WAF or input-filtering rules, lowering the likelihood that unsanitized data reaches the browser.
Requiring language-specific secure-coding standards and automated scanning during the SDLC catches missing output encoding or improper neutralization of untrusted data before the software reaches production.
Application security requirements explicitly call for neutralization of script-related HTML tags.
Secure-coding standards, SAST scans and removal of insecure code samples together eliminate the failure to neutralize script content that produces cross-site scripting flaws.