Skip to content
Fencer Intel
medium 5.0

CVE-2026-63389 json

Filament Curator: Cross-tenant media metadata disclosure via Curator picker search

published 12h ago modified 12h ago also GHSA-828w-6qgx-3rcf

cvss
5.0
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
—
no EPSS score yet
public exploits
0
none known

Summary

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](https://github.com/afa114).

Patch / fix

Is CVE-2026-63389 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by version score vector
GitHub 3.1 5.0 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
packagist awcodes/filament-curator
>=5.0.0, <5.1.1
>=4.0.0, <4.1.1
>=3.2.4, <3.7.8
5.1.1
4.1.1
3.7.8

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.