Summary
Filament has unvalidated ColorColumn and ColorEntry values that can be used for Cross-site Scripting
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.
Impact
Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.
CVE-2024-47186 has a CVSS score of 6.1 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.2.115); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
filament/tables to 3.2.115 or later; filament/infolists to 3.2.115 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2024-47186? CVE-2024-47186 is a medium-severity cross-site scripting (XSS) vulnerability in filament/tables (composer), affecting versions >= 3.0.0, < 3.2.115. It is fixed in 3.2.115. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
- How severe is CVE-2024-47186? CVE-2024-47186 has a CVSS score of 6.1 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which packages are affected by CVE-2024-47186?
filament/tables(composer) (versions >= 3.0.0, < 3.2.115)filament/infolists(composer) (versions >= 3.0.0, < 3.2.115)
- Is there a fix for CVE-2024-47186? Yes. CVE-2024-47186 is fixed in 3.2.115. Upgrade to this version or later.
- Is CVE-2024-47186 exploitable, and should I be worried? Whether CVE-2024-47186 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2024-47186 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2024-47186?
- Upgrade
filament/tablesto 3.2.115 or later - Upgrade
filament/infoliststo 3.2.115 or later
- Upgrade