GHSA-9h9q-qhxg-89xr is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in filament/tables. A fix is available for filament/tables — see the affected versions and patch details below.
Filament has unvalidated ColorColumn and ColorEntry values that can be used for Cross-site Scripting
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-9h9q-qhxg-89xr.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-9h9q-qhxg-89xr plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
filament/tables🐘filament/infolistsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Summary
If values passed to a ColorColumn or ColumnEntry are not valid and contain a specific set of characters, applications are vulnerable to XSS attack against a user who opens a page on which a color column or entry is rendered.
Versions of Filament from v3.0.0 through v3.2.114 are affected.
Please upgrade to Filament v3.2.115.
PoC
For example, using a value such as:
blue;"><script>alert('There\'s a security problem here')</script style="
Would get passed into the @style() Blade directive from Laravel to render the correct background color, where $state contains the value:
<div @style([
"background-color: {$state}" => $state,
])></div>
Since Laravel does not escape special characters within the @style Blade directive, the effective output HTML would be:
<div style="background-color: blue;"><script>alert('There\'s a security problem here')</script style=""></div>
Creating the opportunity for arbitrary JS to run if it was stored in the database.
Response
This vulnerability (in ColorColumn only) was reported by @sv-LayZ, who reported the issue and patched the issue during the evening of 25/09/2024. Thank you Mattis.
The review process concluded on 27/09/2024, which revealed the issue was also present in ColorEntry. This was fixed the same day and Filament v3.2.115 followed to escape any special characters while outputting inline styles like this:
<div @style([
'background-color: ' . e($state) => $state,
])></div>
Although these components are no longer vulnerable to this type of XSS attack, it is good practice to validate colors, and since many Filament users may be accepting color input using the ColorPicker form component, additional color validation documentation was published.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | filament/tables | ≥ 3.0.0&&< 3.2.115 | 3.2.115composer require filament/tables:^3.2.115 |
| 🐘Packagist | filament/infolists | ≥ 3.0.0&&< 3.2.115 | 3.2.115composer require filament/infolists:^3.2.115 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for filament/tables, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update filament/tables to 3.2.115 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9h9q-qhxg-89xr is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-9h9q-qhxg-89xr can be triaged on real exposure rather than presence alone.
Tailored to GHSA-9h9q-qhxg-89xr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-9h9q-qhxg-89xr in your dependencies?
O3 Security finds GHSA-9h9q-qhxg-89xr across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.