Directus has Improper Permission Handling on Deleted Fields

Vulnerability 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.

References

• https://github.com/directus/directus/security/advisories/GHSA-9x5g-62gj-wqf2
• https://github.com/directus/directus/commit/84d7636969083387164ce5d2fd15a65e11e2d0b8