
Cloud Vulnerability DB
A community-led vulnerabilities database
CVE-2026-63389 is a cross-tenant media metadata disclosure vulnerability in the Filament Curator media picker (awcodes/filament-curator) affecting multitenant Filament panel deployments. An authenticated user can retrieve media metadata belonging to other tenants by typing in the Curator media-picker search box, because the search query omits the tenant ownership scope applied by the normal file listing. The vulnerability was introduced in v3.2.4 (when multitenancy support was added), first published in the GitHub Advisory Database on July 6, 2026, and formally disclosed on November 17, 2026. Affected versions are >= 3.2.4, < 3.7.8, >= 4.0.0, < 4.1.1, and >= 5.0.0, < 5.1.1; single-tenant installs are not affected. It carries a CVSS v3.1 base score of 5.0 (Medium) (Github Advisory, v3.7.8 Release).
The root cause is improper access control (CWE-284): CuratorPanel::updatedSearch() constructed its Eloquent query independently of getFiles() and did not apply the filament()->hasTenancy() && $isTenantAware tenant-ownership WHERE clause, allowing the search to match media records across all tenants. A secondary flaw compounded the issue — the orWhere('title'…) chain was not wrapped in a nested query group, so the OR conditions also escaped the isLimitedToDirectory constraint, potentially exposing records from directories outside the intended scope. The fix (commits 17615a2 and c129a36) adds a ->when(filament()->hasTenancy() && $this->isTenantAware, ...) scope before the search conditions and wraps all orWhere clauses in a nested ->where(function ($query) {...}) group (Github Advisory, Patch Commit).
Exploitation allows any authenticated user in a multitenant Filament panel to enumerate media metadata — including file name, title, alt text, caption, description, and storage path — belonging to other tenants via the picker search box. The impact is limited to confidentiality (no integrity or availability impact), but cross-tenant data leakage in SaaS or shared-hosting environments can expose sensitive business assets, reveal internal file structures, and violate tenant data isolation guarantees. The secondary directory-scope bypass additionally allows retrieval of media outside the attacker's permitted directory, broadening the exposure surface (Github Advisory).
No public proof-of-concept exploit code or in-the-wild exploitation has been reported. The vulnerability requires only a low-privilege authenticated session within a multitenant Filament panel — no special roles or elevated permissions are needed. The attack is network-accessible, low complexity, and requires no user interaction, making it straightforward to exploit once an attacker has panel access. The CVE status is currently "Reserved" and no EPSS score or CISA KEV listing is available at this time (Github Advisory).
awcodes/filament-curator package (versions 3.2.4–3.7.7, 4.0.0–4.1.0, or 5.0.0–5.1.0) with Curator tenant awareness enabled.updatedSearch() method fires a Livewire update that executes the vulnerable Eloquent query without the tenant ownership scope.isLimitedToDirectory, note that the ungrouped orWhere chain breaks out of the directory constraint, returning results from directories outside the attacker's permitted scope (Github Advisory, Patch Commit).POST to the Filament panel route) triggering updatedSearch on CuratorPanel from a single authenticated user in a short time window, especially with single-character or sequential search terms suggesting enumeration.SELECT statements on the media table without a tenant ownership WHERE clause.search parameter values, returning media metadata from multiple tenants.Upgrade to a patched version immediately: 3.7.8, 4.1.1, or 5.1.1 depending on your major version branch. The maintainer explicitly states there are no effective workarounds — disabling tenant awareness removes the boundary entirely rather than fixing the scoping issue. All multitenant deployments using Curator's tenant awareness should treat this as a priority upgrade (Github Advisory, v3.7.8 Release, v4.1.1 Release).
The vulnerability was reported via coordinated disclosure by security researcher Afsana Alijabarova and credited in the GitHub Security Advisory. No significant broader media coverage, vendor statements beyond the advisory, or notable social media commentary has been identified at this time (Github Advisory).
Source: This report was generated using AI
Free Vulnerability Assessment
Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.
Get a personalized demo
"Best User Experience I have ever seen, provides full visibility to cloud workloads."
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
"We know that if Wiz identifies something as critical, it actually is."