Medium

Directus `search` query parameter allows enumeration of non permitted fields

  • Disclosed: 26.03.2025
  • Updated: 11.10.2026 10:22

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.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
npm package directus >= 9.0.0-alpha.4, < 11.5.0 11.5.0

References

CVSS score 5.3/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Weakness (CWE)
CWE-200
Platform
npm
Package
directus
Disclosed
26.03.2025
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-7wq3-jr35-275c - CC BY 4.0

Vulnerability history: directus

All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (58) in the archive
Total entries
58
First → latest
04.2022 07.2026
Without a fix
0
Exploited in attacks
0

Severity breakdown

  • Critical 2
  • High 19
  • Medium 34
  • Low 3

Disclosures per year

  1. 2022: 4
  2. 2023: 8
  3. 2024: 14
  4. 2025: 17
  5. 2026: 15
Severity:
  1. High · 7.7 CVE-2026-61835 < 12.0.0 12.0.0
  2. High · 8.7 CVE-2026-35408 < 11.17.0 11.17.0
  3. High · 8.6 CVE-2025-30353 >= 9.12.0, < 11.5.0 11.5.0
  4. Directus `search` query parameter allows enumeration of non permitted fields this entry
    Medium · 5.3 CVE-2025-30352 >= 9.0.0-alpha.4, < 11.5.0 11.5.0
  5. High · 7.5 CVE-2024-54151 >= 11.0.0, < 11.3.0 11.3.0
  6. High · 7.4 CVE-2024-45596 < 10.13.3, >= 11.0.0-rc.1, < 11.1.0 10.13.3, 11.1.0
  7. High · 7.5 CVE-2024-39896 >= 9.11, < 10.13.0 10.13.0
  8. High · 6.3 CVE-2024-39701 >= 9.23.0, < 10.6.0 10.6.0
  9. High · 8.2 CVE-2024-27295 < 10.8.3 10.8.3
  10. High · 7.5 CVE-2023-45820 >= 10.4.0, < 10.6.2 10.6.2
  11. High · 7.6 ghsa-22rr-f3p8-5gf8 < 10.6.0 10.6.0
  12. Critical · 9.8 CVE-2022-26969 < 9.7.0 9.7.0

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.