CVE-2026-63389: Filament Curator: cross-tenant media metadata leak via search
GHSA-828w-6qgx-3rcfMEDIUMFilament Curator, a media-manager plugin for Laravel Filament panels, has a missing tenant scope in its media-picker search, so any authenticated user in a multitenant panel can read other tenants' media metadata (names, titles, alt text, captions, descriptions, file paths). This is a medium-severity confidentiality issue (CVSS 5.0, scope changed) with no EPSS score, no public exploit, no Nuclei template and no CISA KEV listing, so near-term mass exploitation is unlikely. The exposure matters most for SaaS platforms that host multiple customers on one Filament panel, because it breaks the tenant isolation boundary and can reveal confidential customer content or internal file paths. With 517 downstream dependents and 85 other CVEs in the same package, affected teams should treat it as routine but prompt patching: upgrade to 5.1.1 (or 3.7.8 / 4.1.1 on older branches). There is no workaround, and disabling tenant awareness makes the exposure worse.
What is the risk?
Medium. Exploitation is trivial for any authenticated user (low privileges, no user interaction, network reachable): typing a query into the media-picker search box. Impact is limited to low confidentiality loss of metadata, with no integrity or availability effect. Scope is changed because the flaw crosses the tenant boundary. Only deployments using Filament multitenancy with Curator tenant awareness enabled are affected; single-tenant installs are not. No active exploitation, public exploit or scanner template is known, and EPSS is unavailable. The AI link is indirect: the component is classed as an ML UI, and leaked media metadata could expose assets feeding AI content or dataset workflows.
How does the attack unfold?
What systems are affected?
| Package | Ecosystem | Vulnerable Range | Patched |
|---|---|---|---|
| Panel | composer | >= 5.0.0, < 5.1.1 | 5.1.1 |
Do you use Panel? You're affected.
How severe is it?
What is the attack surface?
What should I do?
1 step1) Upgrade awcodes/filament-curator to 5.1.1 (5.x), 4.1.1 (4.x) or 3.7.8 (3.x) via Composer. 2) There is no workaround; do not disable tenant awareness, as that removes the boundary entirely. 3) Inventory Filament panels that use multitenancy together with Curator, since only those are affected. 4) Review application and database query logs for unusual media-picker search activity from tenant users, especially queries returning records owned by other tenants. 5) Review media titles, captions and descriptions for sensitive content, and if exposure is suspected, assess notification obligations for affected tenants. 6) Add tenant-isolation tests to CI for search and picker endpoints.
How is it classified?
Which compliance frameworks are affected?
This CVE is relevant to:
Frequently Asked Questions
What is CVE-2026-63389?
Filament Curator, a media-manager plugin for Laravel Filament panels, has a missing tenant scope in its media-picker search, so any authenticated user in a multitenant panel can read other tenants' media metadata (names, titles, alt text, captions, descriptions, file paths). This is a medium-severity confidentiality issue (CVSS 5.0, scope changed) with no EPSS score, no public exploit, no Nuclei template and no CISA KEV listing, so near-term mass exploitation is unlikely. The exposure matters most for SaaS platforms that host multiple customers on one Filament panel, because it breaks the tenant isolation boundary and can reveal confidential customer content or internal file paths. With 517 downstream dependents and 85 other CVEs in the same package, affected teams should treat it as routine but prompt patching: upgrade to 5.1.1 (or 3.7.8 / 4.1.1 on older branches). There is no workaround, and disabling tenant awareness makes the exposure worse.
Is CVE-2026-63389 actively exploited?
No confirmed active exploitation of CVE-2026-63389 has been reported, but organizations should still patch proactively.
How to fix CVE-2026-63389?
1) Upgrade awcodes/filament-curator to 5.1.1 (5.x), 4.1.1 (4.x) or 3.7.8 (3.x) via Composer. 2) There is no workaround; do not disable tenant awareness, as that removes the boundary entirely. 3) Inventory Filament panels that use multitenancy together with Curator, since only those are affected. 4) Review application and database query logs for unusual media-picker search activity from tenant users, especially queries returning records owned by other tenants. 5) Review media titles, captions and descriptions for sensitive content, and if exposure is suspected, assess notification obligations for affected tenants. 6) Add tenant-isolation tests to CI for search and picker endpoints.
What systems are affected by CVE-2026-63389?
This vulnerability affects the following AI/ML architecture patterns: Multi-tenant SaaS admin panels, ML/AI content management UIs, Laravel Filament applications, Media and asset management for AI-generated content.
What is the CVSS score for CVE-2026-63389?
CVE-2026-63389 has a CVSS v3.1 base score of 5.0 (MEDIUM).
What is the AI security impact?
Affected AI Architectures
MITRE ATLAS Techniques
AML.T0012Valid AccountsAML.T0036Data from Information RepositoriesCompliance Controls Affected
What are the technical details?
Original Advisory
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).
Exploitation Scenario
An attacker holds a legitimate low-privilege account in one tenant of a multi-tenant Filament-based AI content platform. They open the Curator media picker and type common search terms such as 'invoice', 'prompt', 'logo' or 'confidential'. Because the search query skips the tenant ownership clause, results come back from every tenant, and the unbounded OR conditions also ignore directory limits. The attacker harvests titles, captions, descriptions and storage paths of other customers' media, then uses them for competitive intelligence, social engineering, or to guess direct file URLs for further access.
Weaknesses (CWE)
CWE-284 — Improper Access Control: The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
- [Architecture and Design, Operation] Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
- [Architecture and Design] Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
Source: MITRE CWE corpus.
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:NReferences
- github.com/advisories/GHSA-828w-6qgx-3rcf
- github.com/awcodes/filament-curator/commit/17615a20924b7cd373595f6ec56abb79f23cdf7f
- github.com/awcodes/filament-curator/commit/c129a3692d7ef1c9923a2be7402704b20ed4f243
- github.com/awcodes/filament-curator/releases/tag/v3.7.8
- github.com/awcodes/filament-curator/releases/tag/v4.1.1
- github.com/awcodes/filament-curator/releases/tag/v5.1.1
- github.com/awcodes/filament-curator/security/advisories/GHSA-828w-6qgx-3rcf
Timeline
Related Vulnerabilities
CVE-2024-1315210.0Mobuy Panel: SQLi allows unauthenticated DB takeover
Same package: panelCVE-2026-528559.9Pterodactyl Wings: egg template leaks daemon secrets
Same package: panelCVE-2026-541589.9SiYuan: XSS→RCE via workspace sync in Electron app
Same package: panelCVE-2026-477449.9Shopper: RBAC bypass allows full admin takeover
Same package: panelCVE-2026-556349.9Pimcore: DataObject field-name injection → RCE
Same package: panel