Advisory details:
github_osv / GHSA-9x5g-62gj-wqf2
| Advisory ID | github_osv/GHSA-9x5g-62gj-wqf2 |
| Aliases |
CVE-2025-64746
|
| Summary | 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 permissions have been fully cleared. 1. Create a collection named test_collection. 2. Add a field called secret_field. 3. Assign a role with read permissions specifically tied to secret_field. 4. Remove the secret_field from the collection. 5. Create a new field with the exact same name secret_field. 6. Notice that the previously assigned permissions are still active, granting access to the newly created field without reconfiguration. ### Impact When creating new fields with the same name as previously deleted fields it may inherit the permissions of that previously deleted field. This can potentially result in accidentally giving access to this new field in existing policies. |
| Status | Published |
| Exploitability | 0.5 |
| Weighted Severity | 4.1 |
| Risk | 2.0 |
| Affected and Fixed Packages | Package Details |
| Introduced and Fixed Package Commit Patches | Package Commit Patches Details |
| CWE-284 | Improper Access Control |
| CWE-863 | Incorrect Authorization |
| System | Score | Found at |
|---|---|---|
| cvssv3.1 | 4.6 | https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2025/11/GHSA-9x5g-62gj-wqf2/GHSA-9x5g-62gj-wqf2.json |
| generic_textual | MODERATE |
| Reference id | Reference type | URL |
|---|---|---|
| https://github.com/directus/directus | ||
| https://github.com/directus/directus/commit/84d7636969083387164ce5d2fd15a65e11e2d0b8 | ||
| CVE-2025-64746 | https://nvd.nist.gov/vuln/detail/CVE-2025-64746 | |
| GHSA-9x5g-62gj-wqf2 | https://github.com/directus/directus/security/advisories/GHSA-9x5g-62gj-wqf2 |
No EPSS data available for this advisory.
| Patch URL | |
|---|---|
| There are no known patches. | |
| Attack Vector (AV) | Attack Complexity (AC) | Privileges Required (PR) | User Interaction (UI) | Scope (S) | Confidentiality Impact (C) | Integrity Impact (I) | Availability Impact (A) |
|---|---|---|---|---|---|---|---|
network adjacent_network local physical |
low high |
none low high |
none required |
unchanged changed |
high low none |
high low none |
high low none |
Vector: SSVCv2/E:P/A:N/T:P/P:M/B:A/M:M/D:T/2025-11-13T21:18:13Z/
Decision: Track
Source URL: https://github.com/cisagov/vulnrichment/blob/develop/2025/64xxx/CVE-2025-64746.json
Source Advisory: vulnrichment/CVE-2025-64746
[{'Exploitation': 'poc'},
{'Automatable': 'no'},
{'Technical Impact': 'partial'},
{'Mission Prevalence': 'minimal'},
{'Public Well-being Impact': 'material'},
{'Mission & Well-being': 'medium'}]