GHSA-9X5G-62GJ-WQF2

Vulnerability from github – Published: 2025-11-14 21:45 – Updated: 2025-11-14 21:45
VLAI?
Summary
Directus has Improper Permission Handling on Deleted Fields
Details

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.

Severity ?
4.6 (Medium)
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N
Show details on source website
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "directus"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "11.13.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2025-64746"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-284",
      "CWE-863"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2025-11-14T21:45:15Z",
    "nvd_published_at": "2025-11-13T21:15:54Z",
    "severity": "MODERATE"
  },
  "details": "### Summary\nDirectus 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.\n\n### Details\nWhen 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.  \nThis behavior can unintentionally grant roles access to data they should not be able to read or modify.\n\nThe issue is particularly risky in multi-tenant or production environments, where administrators may reuse field names, assuming old permissions have been fully cleared.\n\n\t1.\tCreate a collection named test_collection.\n\t2.\tAdd a field called secret_field.\n\t3.\tAssign a role with read permissions specifically tied to secret_field.\n\t4.\tRemove the secret_field from the collection.\n\t5.\tCreate a new field with the exact same name secret_field.\n\t6.\tNotice that the previously assigned permissions are still active, granting access to the newly created field without reconfiguration.\n\n### Impact\n\nWhen 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.",
  "id": "GHSA-9x5g-62gj-wqf2",
  "modified": "2025-11-14T21:45:15Z",
  "published": "2025-11-14T21:45:15Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/directus/directus/security/advisories/GHSA-9x5g-62gj-wqf2"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-64746"
    },
    {
      "type": "WEB",
      "url": "https://github.com/directus/directus/commit/84d7636969083387164ce5d2fd15a65e11e2d0b8"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/directus/directus"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Directus has Improper Permission Handling on Deleted Fields"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.