CVE-2026-63389: Filament Curator: Cross-tenant media metadata disclosure via Curator picker search
Summary
In multitenant Filament panels, an authenticated user could retrieve media metadata belonging to other tenants by typing in the Curator media-picker search box. The search query omitted the tenant ownership scope that the normal file listing applies.
Details
CuratorPanel::updatedSearch() built its Eloquent query independently of getFiles() and did not apply the filament()->hasTenancy() && $isTenantAware tenant-ownership where clause. As a result, the search matched media across all tenants. A secondary flaw compounded it: the orWhere('title'…) chain was not wrapped in a nested group, so the OR conditions also broke out of the isLimitedToDirectory constraint.
The issue was introduced in v3.2.4, when multitenancy support was added to the media picker.
Impact
- Who: any authenticated user with access to a panel that uses the Curator picker. - What: disclosure of other tenants' media metadata (name, title, alt, caption, description, path, etc.) returned by the search. - Conditions: only affects deployments using Filament multitenancy with Curator's tenant awareness enabled. Single-tenant installs are not affected.
Patches
Fixed in 3.7.8, 4.1.1, and 5.1.1 by applying the tenant scope to the search query and grouping the search terms so they cannot escape the directory/tenant constraints. Upgrade to a patched version.
Workarounds
None other than upgrading. Disabling tenant awareness does not help (it removes the boundary entirely).
Credit
Reported via coordinated disclosure by Afsana Alijabarova.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
composer/awcodes/filament-curatorto a version that resolves this vulnerability.Fixed in 3.7.8 - Upgrade
Upgrade
composer/awcodes/filament-curatorto a version that resolves this vulnerability.Fixed in 4.1.1 - Upgrade
Upgrade
composer/awcodes/filament-curatorto a version that resolves this vulnerability.Fixed in 5.1.1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 3.7.8 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 4.1.1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 5.1.1
Event History
Frequently Asked Questions
Which deployments are affected?
Only Filament deployments using multitenancy with Curator tenant awareness enabled are affected. Single-tenant installations are not affected.
What access does an attacker need?
An attacker needs to be authenticated and have access to a panel that uses the Curator media picker. They can trigger the issue by entering searches in the picker search box.
What information can be exposed?
Search results can disclose media metadata belonging to other tenants, including names, titles, alt text, captions, descriptions, and paths. The issue is limited to metadata disclosure; no integrity or availability impact is described.
How can I determine whether my deployment is vulnerable?
Check whether the deployment uses Filament multitenancy and has Curator tenant awareness enabled, then test the media-picker search as a tenant user for results from another tenant. The vulnerable behavior was introduced in v3.2.4.
Which versions contain fixes?
The issue is fixed in versions 3.7.8, 4.1.1, and 5.1.1. The fixes apply tenant ownership scoping to the search query.