{"vulnerability": "cve-2025-30352", "sightings": [{"uuid": "0117b9f8-8369-41cc-ae34-9d312dc12f35", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-30352", "type": "seen", "source": "https://t.me/cvedetector/21202", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-30352 - Directus Unrestricted Field Enumerability\", \n  \"Content\": \"CVE ID : CVE-2025-30352 \nPublished : March 26, 2025, 6:15 p.m. | 31\u00a0minutes ago \nDescription : Directus is a real-time API and App dashboard for managing SQL database content. Starting in version 9.0.0-alpha.4 and prior to version 11.5.0, the `search` query parameter allows users with access to a collection to filter items based on fields they do not have permission to view. This allows the enumeration of unknown field contents. The searchable columns (numbers & strings) are not checked against permissions when injecting the `where` clauses for applying the search query. This leads to the possibility of enumerating those un-permitted fields. Version 11.5.0 fixes the issue. \nSeverity: 5.3 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"26 Mar 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-03-26T20:34:48.000000Z"}, {"uuid": "59224316-3709-4ecd-a74c-3a7c9eee55ee", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-30352", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/9122", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-30352\n\ud83d\udd25 CVSS Score: 5.3 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N)\n\ud83d\udd39 Description: Directus is a real-time API and App dashboard for managing SQL database content. Starting in version 9.0.0-alpha.4 and prior to version 11.5.0, the `search` query parameter allows users with access to a collection to filter items based on fields they do not have permission to view. This allows the enumeration of unknown field contents. The searchable columns (numbers & strings) are not checked against permissions when injecting the `where` clauses for applying the search query. This leads to the possibility of enumerating those un-permitted fields. Version 11.5.0 fixes the issue.\n\ud83d\udccf Published: 2025-03-26T17:18:39.567Z\n\ud83d\udccf Modified: 2025-03-27T15:15:07.652Z\n\ud83d\udd17 References:\n1. https://github.com/directus/directus/security/advisories/GHSA-7wq3-jr35-275c\n2. https://github.com/directus/directus/commit/ac5a9964d9926f20dc063a74cb417dc7bbad676d", "creation_timestamp": "2025-03-27T15:26:55.000000Z"}, {"uuid": "c1beb98a-5dc9-48d8-bba3-418d84f9cafd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-30352", "type": "published-proof-of-concept", "source": "https://github.com/directus/directus/security/advisories/GHSA-7wq3-jr35-275c", "content": "", "creation_timestamp": "2025-03-26T15:04:58.000000Z"}]}