filamentphp filament up to 3.2.114 ColorColumn/ColumnEntry cross site scripting

Summaryinfo

A vulnerability has been found in filamentphp filament up to 3.2.114 and classified as problematic. The impacted element is an unknown function. The manipulation of the argument ColorColumn/ColumnEntry leads to cross site scripting. This vulnerability is listed as CVE-2024-47186. The attack may be initiated remotely. There is no available exploit. The affected component should be upgraded.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in filamentphp filament up to 3.2.114. This issue affects an unknown part. The manipulation of the argument ColorColumn/ColumnEntry with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. Impacted is integrity. The summary by CVE is:

Filament is a collection of full-stack components for Laravel development. Versions of Filament from v3.0.0 through v3.2.114 are affected by a cross-site scripting (XSS) vulnerability. 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. Filament v3.2.115 fixes this issue.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2024-47186 since 09/20/2024. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.

Upgrading to version 3.2.115 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch df7989352464d08eda5837ef50f9997fad902316 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• filamentphp

Name

• filament

Version

• 3.2.114

License

• open-source

Website

• Product: https://github.com/filamentphp/filament/

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion