VulnerabilityPublished 13 Nov 2025Updated 15 Nov 2025

CVE-2025-64748: Directus's conceal fields are searchable if read permissions enabled

Affects directusSource GCVE Database

Compare

Authoritative record:CVE-2025-64748· Medium 6.5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 11.13.0 when convenient.

Data as of 13 Nov 2026, 19:07 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (GitHub_M)	CVSS 3.1	6.5

Patch: Available – fixed in 11.13.0, 32.0.0

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade directus to 11.13.0; @directus/api to 32.0.0.

Affected software

Product	Affected	Fixed in
npmdirectus	Affected <11.13.0	Fixed in 11.13.0
npm@directus/api	Affected <32.0.0	Fixed in 32.0.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in Directus versions 11.13.0 and 32.0.0 that addresses this issue. Users should upgrade to these or later versions to remediate the vulnerability. Until patched, review and restrict read permissions on sensitive fields to prevent unauthorized search operations. No indication from the vendor advisory suggests that the issue is already mitigated or requires no action.

Description

Directus versions prior to 11.13.0 and 32.0.0 contain a vulnerability where authenticated users with read permissions can search concealed sensitive fields such as tokens, TFA secrets, and password hashes. Although the actual values are masked in search results, the presence of matching records confirms the existence of specific sensitive data. This enables enumeration attacks that can verify valid authentication tokens and identify accounts with compromised passwords by cross-referencing known password hashes. The vulnerability arises from default permissions granting broad read access, increasing exposure risk.

Impact

The vulnerability allows attackers to confirm the existence of sensitive data such as authentication tokens and password hashes without revealing the actual values. This enables token enumeration and identification of accounts with compromised passwords by matching against publicly available hash databases. The increased attack surface due to default read permissions means many deployments are exposed by default, raising the risk of targeted account compromise and unauthorized access.

Summary

CVE-2025-64748 affects Directus installations before versions 11.13.0 and 32.0.0. Authenticated users with read permissions can perform search operations on concealed fields within the directus_users collection, including sensitive fields like token, tfa_secret, and password. While the actual sensitive values remain masked in the returned records, the ability to detect matching records allows attackers to enumerate valid tokens and identify accounts using known compromised password hashes. This vulnerability is exacerbated by default recommended permissions that grant full read access to user role records, thereby exposing sensitive data indirectly through search functionality.

CWE-201Insertion of Sensitive Information Into Sent Data (opens in a new tab)
Base weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.
Requirements
Specify which data in the software should be regarded as sensitive. Consider which types of users should have access to which types of data.
Implementation
Ensure that any possibly sensitive data specified in the requirements is verified with designers to ensure that it is either a calculated risk or mitigated elsewhere.
System Configuration
Setup default error messages so that unexpected errors do not disclose sensitive information.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Choosing Message Identifier (opens in a new tab)
Exploiting Incorrectly Configured SSL/TLS (opens in a new tab)
WiFi MAC Address Tracking (opens in a new tab)
WiFi SSID Tracking (opens in a new tab)
Cellular Broadcast Message Request (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 13 Nov 2026, 19:07 UTC

WeaknessesCWE-201

Technical details

References

Community reviews

Related threats