CVE-2026-63389 is a medium-severity (CVSS 5) vulnerability in awcodes/filament-curator. A fix is available for awcodes/filament-curator — see the affected versions and patch details below.
Filament Curator: Cross-tenant media metadata disclosure via Curator picker search
Real-World Exposure
awcodes/filament-curator🐘awcodes/filament-curator🐘awcodes/filament-curatorReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
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 Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | awcodes/filament-curator | ≥ 5.0.0&&< 5.1.1 | 5.1.1composer require awcodes/filament-curator:^5.1.1 |
| 🐘Packagist | awcodes/filament-curator | ≥ 4.0.0&&< 4.1.1 | 4.1.1composer require awcodes/filament-curator:^4.1.1 |
| 🐘Packagist | awcodes/filament-curator | ≥ 3.2.4&&< 3.7.8 | 3.7.8composer require awcodes/filament-curator:^3.7.8 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for awcodes/filament-curator, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update awcodes/filament-curator to 5.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-63389 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2026-63389 in your dependencies?
Find it across Packagist, including transitive dependencies.