CVE-2025-64746
published 2025-11-13CVE-2025-64746: 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…
PriorityP429medium5.4CVSS 3.1
AVNACLPRNUIRSUCLILAN
EPSS
0.16%
5.9th percentile
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
3 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| directus | directus | < 11.13.0 | 11.13.0 |
| directus | directus | >= 0 < 11.13.0 | 11.13.0 |
| monospace | directus | < 11.13.0 | 11.13.0 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
Directus has Improper Permission Handling on Deleted Fields
osv·2025-11-14
CVE-2025-64746 [MEDIUM] Directus has Improper Permission Handling on Deleted Fields
Directus has Improper Permission Handling on Deleted Fields
### Summary
Directus does not properly clean up field-level permissions when a field is deleted. If a new field with the same name is created later, the system automatically re-applies the old permissions, which can lead to unauthorized access.
### Details
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 pe
GHSA
Directus has Improper Permission Handling on Deleted Fields
ghsa·2025-11-14
CVE-2025-64746 [MEDIUM] CWE-284 Directus has Improper Permission Handling on Deleted Fields
Directus has Improper Permission Handling on Deleted Fields
### Summary
Directus does not properly clean up field-level permissions when a field is deleted. If a new field with the same name is created later, the system automatically re-applies the old permissions, which can lead to unauthorized access.
### Details
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 pe
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2025-11-13
Published