CVE-2025-64746
BaseFortify
Publication date: 2025-11-13
Last updated on: 2025-12-08
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| monospace | directus | to 11.13.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-284 | The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. |
| CWE-863 | The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs in Directus versions prior to 11.13.0, where when a field is deleted from a collection, its permissions are not properly removed. The permissions table retains references to the deleted field. If a new field is later created with the same name, it inherits the old permissions, potentially granting roles access to data they should not have. This creates a security gap, especially in environments where field names are reused.
How can this vulnerability impact me? :
The vulnerability can lead to unauthorized access or modification of data because roles may inherit outdated permissions for newly created fields with reused names. This can expose sensitive information or allow unintended data changes, posing a security risk particularly in multi-tenant or production environments.
What immediate steps should I take to mitigate this vulnerability?
Upgrade Directus to version 11.13.0 or later, as this version fixes the issue by properly cleaning up field-level permissions when fields are deleted.