CVE-2025-64748

A vulnerability allows authenticated users to search concealed/sensitive fields when they have read permissions. While actual values remain masked (****), successful matches can be detected through returned records, enabling enumeration attacks on sensitive data.

Details

The system permits search operations on concealed fields in the directus_users collection, including token, tfa_secret, password. Matching records are returned with masked values, but their presence confirms the searched value exists.

The "Recommended Defaults" for "App Access" grant users full read permissions to their role/user records, inadvertently enabling them to search for any user's tokens, TFA secrets, and password hashes. Attackers can leverage known password hashes from breach databases to identify accounts with compromised passwords.

This vulnerability enables:

• Token enumeration - Verification of valid authentication tokens
• Password hash matching - Identification of accounts using known compromised passwords
• Information disclosure - Confirmation of sensitive value existence without viewing actual data
• Increased attack surface - Default permissions automatically expose all deployments using recommended settings

The risk is particularly high for password fields, where attackers can cross-reference publicly available hash databases to identify vulnerable accounts.

CVE-2025-64748 has a CVSS score of 6.5 (Medium). The vector is network-reachable, low 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.13.0, 32.0.0); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2025-64748? CVE-2025-64748 is a medium-severity security vulnerability in directus (npm), affecting versions < 11.13.0. It is fixed in 11.13.0, 32.0.0.
2. How severe is CVE-2025-64748? CVE-2025-64748 has a CVSS score of 6.5 (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 packages are affected by CVE-2025-64748?
   • directus (npm) (versions < 11.13.0)
   • @directus/api (npm) (versions < 32.0.0)
4. Is there a fix for CVE-2025-64748? Yes. CVE-2025-64748 is fixed in 11.13.0, 32.0.0. Upgrade to this version or later.
5. Is CVE-2025-64748 exploitable, and should I be worried? Whether CVE-2025-64748 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-64748 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-64748?
   • Upgrade directus to 11.13.0 or later
   • Upgrade @directus/api to 32.0.0 or later