Open-Source Security Intelligence

Know every vulnerability
before it knows you.

DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.

Search

GHSA-828w-6qgx-3rcf

MediumCVSS 5 / 10
Published Nov 17, 2026·Last modified Nov 17, 2026
Affected Components(3)
Packagist logoawcodes/filament-curator
3.2.4 – 3.7.8
Packagist logoawcodes/filament-curator
5.0.0 – 5.1.1
Packagist logoawcodes/filament-curator
4.0.0 – 4.1.1
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.

Upload your SBOM

Upload your own SBOM in CycloneDX 1.6 or higher (JSON) directly here to check your vulnerabilities.

Risk Scores
Base Score
5.0

The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker needs basic access or low-level privileges. No user interaction is needed for the attacker to exploit this vulnerability. The vulnerability can affect other systems as well, not just the initial system. There is a low impact on the confidentiality of the information.

Threat Intelligence
4.6

Exploitation attempts have been detected. Elevated vigilance and prompt remediation are advised.

EPSS
N/A

Probability that this vulnerability will be exploited in the wild within the next 30 days.

Exploit
Not available

We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.

Related Vulnerabilities
  • CVE-2026-63389
    Alias

Browse More

Scan your project

Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.

Checkout DevGuard