CVE-2025-30352: Directus `search` query parameter allows enumeration of non permitted fields
Summary
The search query parameter allows users with access to a collection to filter items based on fields they do not have permission to view. This allows the enumeration of unknown field contents.
Details
The searchable columns (numbers & strings) are not checked against permissions when injecting the where clauses for applying the search query. This leads to the possibility of enumerating those un-permitted fields.
PoC
- Create a collection with a string / numeric field, configure the permissions for the public role to not include the field created - Create items with identifiable content in the not permitted field - Query the collection and include the field content in the search parameter - See that results are returned, even tho the public user does not have permission to view the field content
Impact
This vulnerability is a very high impact, as for example Directus instances which allow public read access to the user avatar are vulnerable to have the email addresses, password hashes and potentially admin level access tokens extracted. The admin token and password hash extraction have a caveat, as string fields are only searched with a lower cased version of the search query.
Other sources
Directus is a real-time API and App dashboard for managing SQL database content. Starting in version 9.0.0-alpha.4 and prior to version 11.5.0, the search query parameter allows users with access to a collection to filter items based on fields they do not have permission to view. This allows the enumeration of unknown field contents. The searchable columns (numbers & strings) are not checked against permissions when injecting the where clauses for applying the search query. This leads to the possibility of enumerating those un-permitted fields. Version 11.5.0 fixes the issue.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/directusto a version that resolves this vulnerability.Fixed in 11.5.0 - Upgrade
Upgrade
Directusto a version that resolves this vulnerability.Fixed in 11.5.0
Event History
Frequently Asked Questions
What is the severity of CVE-2025-30352?
CVE-2025-30352 has a severity rating that indicates a significant risk of unauthorized data enumeration.
How do I fix CVE-2025-30352?
To fix CVE-2025-30352, update to a patched version of the affected Directus package beyond version 11.5.0.
What are the potential impacts of CVE-2025-30352?
The potential impacts of CVE-2025-30352 include unauthorized access to sensitive data fields that users do not have permission to view.
Which versions of Directus are affected by CVE-2025-30352?
Directus versions from 9.0.0-alpha.4 up to 11.5.0 are affected by CVE-2025-30352.
Is authentication required to exploit CVE-2025-30352?
Exploitation of CVE-2025-30352 requires users to have access to the collection but does not require further authentication to exploit the vulnerability.