CVE-2025-64748: Directus Directus's Conceal Fields Are Searchable Vulnerability

MODERATE
Advisory Identifier: GHSA-8jpw-gpr4-8cmh
Share
CVSS 6.5
CWE-201
Published
Advisory Summary

CVE-2025-64748 is a MODERATE (CVSS 6.5) directus's conceal fields are searchable vulnerability (CWE-201: Insertion of Sensitive Information Into Sent Data) affecting Directus libraries in the npm ecosystem. The issue involves directus's conceal fields are searchable if read permissions enabled. Remediation is available by upgrading affected packages to version 11.13.0, 32.0.0.

CVE-2025-64748 at a Glance

CVE Identifier CVE-2025-64748
GHSA Identifier GHSA-8jpw-gpr4-8cmh
Severity MODERATE
CVSS v3.1 Base Score 6.5
CWE Classification CWE-201: Insertion of Sensitive Information Into Sent Data
Affected Product Directus
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 6.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2025-64748

To remediate this vulnerability, upgrade all affected Directus dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

directus fixed: 11.13.0 
npm install directus@11.13.0
@directus/api fixed: 32.0.0 
npm install @directus/api@32.0.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls directus

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2025-64748, inspect your project dependencies using npm:

npm ls directus

Analyze the terminal output to locate any version of Directus in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 11.13.0), your application is affected.

Note: The npm ls directus command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-201: Insertion of Sensitive Information Into Sent Data, where the code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor. In Directus, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary 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. # Impact 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 Affected Directus Versions

2 component(s)
Fixed Versions:
11.13.032.0.0
Product / Package Ecosystem Affected Versions Fixed Version
directus
npm/directus
npm
< 11.13.0
11.13.0
@directus/api
npm/@directus/api
npm
< 32.0.0
32.0.0

References

GitHub Advisory / Wiki ADVISORY
https://github.com/directus/directus/security/advisories/GHSA-8jpw-gpr4-8cmh
NVD — CVE-2025-64748 NVD
https://nvd.nist.gov/vuln/detail/CVE-2025-64748
Security Fix Commit FIX COMMIT
https://github.com/directus/directus/commit/7737d56e096f95edfbdf861a3c08999ad31ce204
Directus Source Repository REPOSITORY
https://github.com/directus/directus

Frequently Asked Questions

What is CVE-2025-64748?
CVE-2025-64748 is a security vulnerability in Directus involving Directus's conceal fields are searchable if read permissions enabled under CWE-201: Insertion of Sensitive Information Into Sent Data.
Which Directus versions are affected?
Affected versions include releases prior to 11.13.0, 32.0.0 across affected packages: directus, @directus/api.
What version fixes CVE-2025-64748?
Upgrading to 11.13.0, 32.0.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is directus affected?
Yes, directus is affected in releases prior to 11.13.0. Upgrade your dependency to 11.13.0 or later.
Is @directus/api affected?
Yes, @directus/api is affected in releases prior to 32.0.0. Upgrade your dependency to 32.0.0 or later.
What is the CVSS score of CVE-2025-64748?
CVE-2025-64748 has a CVSS v3.1 base score of 6.5 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2025-64748?
CVE-2025-64748 is classified under CWE-201: Insertion of Sensitive Information Into Sent Data (The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.).
How can I check npm dependencies for CVE-2025-64748?
Run the dependency tree command: 'npm ls directus'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-8jpw-gpr4-8cmh",
  "modified" : "2025-11-15T03:15:27Z",
  "published" : "2025-11-13T23:06:41Z",
  "aliases" : [ "CVE-2025-64748" ],
  "summary" : "Directus's conceal fields are searchable if read permissions enabled",
  "details" : "## Summary\n\nA 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.\n\n## Details\n\nThe 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.\n\nThe \"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.\n\n# Impact\n\nThis vulnerability enables:\n- **Token enumeration** - Verification of valid authentication tokens\n- **Password hash matching** - Identification of accounts using known compromised passwords\n- **Information disclosure** - Confirmation of sensitive value existence without viewing actual data\n- **Increased attack surface** - Default permissions automatically expose all deployments using recommended settings\n\nThe risk is particularly high for password fields, where attackers can cross-reference publicly available hash databases to identify vulnerable accounts.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "directus"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "11.13.0"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@directus/api"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "32.0.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/directus/directus/security/advisories/GHSA-8jpw-gpr4-8cmh"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-64748"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/directus/directus/commit/7737d56e096f95edfbdf861a3c08999ad31ce204"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/directus/directus"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-201" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-11-13T23:06:41Z",
    "nvd_published_at" : "2025-11-13T22:15:52Z"
  }
}