Headline
GHSA-7wq3-jr35-275c: 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
searchparameter - 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.
- GitHub Advisory Database
- GitHub Reviewed
- CVE-2025-30352
Directus `search` query parameter allows enumeration of non permitted fields
Moderate severity GitHub Reviewed Published Mar 26, 2025 in directus/directus • Updated Mar 26, 2025
Package
npm directus (npm)
Affected versions
>= 9.0.0-alpha.4, < 11.5.0
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.
References
- GHSA-7wq3-jr35-275c
- https://nvd.nist.gov/vuln/detail/CVE-2025-30352
- directus/directus@ac5a996
Published to the GitHub Advisory Database
Mar 26, 2025
Last updated
Mar 26, 2025