Vulnerability · Published Nov 13, 2025 · Assigned by GitHub_M

CVE-2025-64746Directus has Improper Permission Handling on Deleted Fields

Medium 4.6

In plain English

A medium-severity improper access control in directus from directus. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 11% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)4.6Medium
Exploit odds (30 days)0.2%top 89.5% of all CVEs
Exploited in the wildNo reportsCISA SSVC: poc
Attack toolingNoneno public tooling known

Official description

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 packages & fixed versions

EcosystemPackageFixed inAdvisory
npmdirectus11.13.0GHSA-9x5g-62gj-wqf2

Affected products (as reported)

VendorProductVersions
directus directus < 11.13.0

Weakness: CWE-284, CWE-863 · Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N

References