vulnerability / NVI-00003440 / Revision 2
Filament has unvalidated ColorColumn and ColorEntry values that can be used for Cross-site Scripting
OSV carries this publisher advisory for filament/tables, filament/infolists. This is an aggregated source copy; consult the original publisher and compare update dates.
This report has not inspected your inventory, configuration, deployed build, reachability or evidence. A catalog listing and a severity score do not establish exposure or compromise.
01 / Meaning
Why it matters
Published affected context helps an owner decide what evidence to gather. This report has not examined your application.
6.1 MEDIUM (3.1)
security-advisories@github.com severity; no combined Null risk score.
6.1 MEDIUM (3.1)
nvd@nist.gov severity; no combined Null risk score.
02 / Applicability
The affected context
Affected versions, configuration prerequisites and known exclusions are public. Confirm each one against the deployed service.
filament/tables
source listedECOSYSTEM: introduced 3.0.0; fixed 3.2.115
### 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: ```html blue;">alert('There\'s a security problem here') $state, ])> ``` Since Laravel does not escape special characters within the `@style` Blade directive, the effective output HTML would be: ```html alert('There\'s a security problem here') ``` 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 is
filament/infolists
source listedECOSYSTEM: introduced 3.0.0; fixed 3.2.115
### 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: ```html blue;">alert('There\'s a security problem here') $state, ])> ``` Since Laravel does not escape special characters within the `@style` Blade directive, the effective output HTML would be: ```html alert('There\'s a security problem here') ``` 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 is
03 / Response
What to do next
- vendor patch
The original advisory lists fixed boundaries 3.2.115 for filament/tables. Confirm the publisher’s latest guidance.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database via OSV
- vendor patch
The original advisory lists fixed boundaries 3.2.115 for filament/infolists. Confirm the publisher’s latest guidance.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database via OSV
- investigate
Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. NIST National Vulnerability Database
A fixed release is not deployment evidence.
Check current vendor support and compatibility. After making a change, verify the deployed build and relevant runtime conditions. Keep the evidence, owner and time. An updated lockfile alone does not prove what is running.
04 / Limits
What this report cannot establish
- Customer inventory, deployment, reachability and exploitation have not been inspected.
- NVD lastModified does not establish freshness of every associated CPE record.
05 / Provenance
Sources you can inspect
Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.
- GHSA-9h9q-qhxg-89xr ↗
GitHub Advisory Database via OSV · vendor advisory
Observed . GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.
- CVE-2024-47186 ↗
NIST National Vulnerability Database · official catalog
Observed . This product uses data from the NVD API but is not endorsed or certified by the NVD.
Public revision history
Only published revisions appear here. Routine fetches do not create a material-change event.
- Revision 2 ·
Source facts changed; compare the preserved prior revision.
- Revision 1 ·
First indexed by Null; source disclosure date is shown separately.