CVE-2025-24353: Directus allows privilege escalation using Share feature
Summary When sharing an item, user can specify an arbitrary role. It allows user to use a higher-privileged role to see fields that otherwise the user should not be able to see. Details Specifying role on share should be available only for admins. The current flow has a security flaw. Each other role should allow to share only in the context of the same role.
Published Jan 23, 2025 · Updated Feb 11, 2025
Affected packages
directus
- Ecosystem
- npm
- Affected
- < 11.2.0
- Fixed in
- 11.2.0
- Check
npm ls directus
@directus/app
- Ecosystem
- npm
- Affected
- < 13.3.1
- Fixed in
- 13.3.1
- Check
npm ls @directus/app
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
When sharing an item, user can specify an arbitrary role. It allows user to use a higher-privileged role to see fields that otherwise the user should not be able to see.
Details
Specifying role on share should be available only for admins. The current flow has a security flaw.
Each other role should allow to share only in the context of the same role. As there is no role hierarchy in Directus, it is impossible to tell which role is _higher_ or _lower_, so only admins should be able to specify the role for share.
Optionally, instead of specifying a role, shareer* should be able to specify which fields (limited to fields shareer sees) are available on shared item. Similarily to import.
*_shareer_ - a person that creates a share link to item
PoC
- Create a collection with a secret field.
- Create role A that sees the secret field
- Create role B that does not see the secret field, but can use share feature.
- Create item with secret field filled.
- Use account with role B to share the object as role A and gain unauthorized access to secret value.
Here's video example: https://www.youtube.com/watch?v=DbV4IxbWzN4 I had to upload it to YouTube, because GitHub allows only 10MB videos.
Impact
Impacted are instances that use the share feature and have specific roles hierarchy and fields that are not visible for certain roles.
Credited to viters, m3t3kh4n.
References
- https://github.com/directus/directus/security/advisories/GHSA-pmf4-v838-29hg
- https://nvd.nist.gov/vuln/detail/CVE-2025-24353
- https://github.com/directus/directus/pull/23716
- https://github.com/directus/directus/commit/e288a43a79613dada905da683f4919c6965ac804
- https://github.com/directus/directus/releases/tag/v11.2.0
- https://www.youtube.com/watch?v=DbV4IxbWzN4
- https://github.com/advisories/GHSA-pmf4-v838-29hg
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-129239
Directus: Share update allows reassigning user_created and role
medium6.5Nov 16, 2026CVE-2026-61835
Directus: SSRF Protection Bypass via 0.0.0.0 in File Import
high7.7Jul 20, 2026CVE-2026-61836
Directus: Authorization-dependent response served from unsegmented cache key
high8.6Jul 20, 2026CVE-2026-35408
Directus: Missing Cross-Origin Opener Policy
high8.7Apr 4, 2026CVE-2026-35409
Directus: SSRF Protection Bypass via IPv4-Mapped IPv6 Addresses in File Import
high7.7Apr 4, 2026CVE-2026-35410
Directus: Open Redirect via Parser Bypass in OAuth2/SAML Authentication Flow
medium6.1Apr 4, 2026
