What is the CVSS score of CVE-2025-64746?

CVE-2025-64746 has a CVSS 3.1 base score of 4.6 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N. EPSS exploitation probability: 0.1%.

Which versions of Directus are affected by CVE-2025-64746?

Organizations using Directus should be aware of moderate risk from CVE-2025-64746, a improper access control vulnerability rated CVSS 4.6.. A patch is available.

Is there a public PoC exploit available for CVE-2025-64746?

Yes, a public proof-of-concept exploit is available for CVE-2025-64746. Prioritise patching immediately. EPSS: 0.1%.

How to fix or mitigate CVE-2025-64746?

During next maintenance window: Identify affected systems and apply vendor patches when convenient. Vendor patch is available.

Directus CVE-2025-64746

MEDIUM

Improper Access Control (CWE-284)

2025-11-13 security-advisories@github.com

Authentication Bypass Directus

4.6

CVSS 3.1 · GitHub Advisory

Severity by source

GitHub Advisory PRIMARY

4.6 MEDIUM

AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

Required

Scope

Unchanged

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

Analysis Generated

Mar 28, 2026 - 19:22 vuln.today

Patch released

Mar 28, 2026 - 19:22 nvd

Patch available

PoC Detected

Dec 08, 2025 - 14:58 vuln.today

Public exploit code

CVE Published

Nov 13, 2025 - 21:15 nvd

MEDIUM 4.6

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

2 npm packages depend on directus (1 direct, 1 indirect)

Ecosystem-wide dependent count for version 11.13.0.

DescriptionGitHub Advisory

Directus is a real-time API and App dashboard for managing SQL database content. Prior to version 11.13.0, Directus does not properly clean up field-level permissions when a field is deleted. When a field is removed from a collection, its reference in the permissions table remains intact. This stale reference creates a security gap: if another field is later created using the same name, it inherits the outdated permission entry. This behavior can unintentionally grant roles access to data they should not be able to read or modify. The issue is particularly risky in multi-tenant or production environments, where administrators may reuse field names, assuming old permissions have been fully cleared. Version 11.13.0 fixes the issue.

AnalysisAI

Directus is a real-time API and App dashboard for managing SQL database content. Rated medium severity (CVSS 4.6), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available.

Technical ContextAI

This vulnerability is classified under CWE-284. Directus is a real-time API and App dashboard for managing SQL database content. Prior to version 11.13.0, Directus does not properly clean up field-level permissions when a field is deleted. When a field is removed from a collection, its reference in the permissions table remains intact. This stale reference creates a security gap: if another field is later created using the same name, it inherits the outdated permission entry. This behavior can unintentionally grant roles access to data they should not be able to read or modify. The issue is particularly risky in multi-tenant or production environments, where administrators may reuse field names, assuming old permissions have been fully cleared. Version 11.13.0 fixes the issue. Affected products include: Monospace Directus. Version information: version 11.13.0.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.

CVE-2025-64746 vulnerability details – vuln.today

Back