CVE-2025-30352

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

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.

CVE-2025-30352 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (11.5.0); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2025-30352? CVE-2025-30352 is a medium-severity security vulnerability in directus (npm), affecting versions >= 9.0.0-alpha.4, < 11.5.0. It is fixed in 11.5.0.
2. How severe is CVE-2025-30352? CVE-2025-30352 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of directus are affected by CVE-2025-30352? directus (npm) versions >= 9.0.0-alpha.4, < 11.5.0 is affected.
4. Is there a fix for CVE-2025-30352? Yes. CVE-2025-30352 is fixed in 11.5.0. Upgrade to this version or later.
5. Is CVE-2025-30352 exploitable, and should I be worried? Whether CVE-2025-30352 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-30352 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-30352? Upgrade directus to 11.5.0 or later.