
Loading

Loading
We use strictly necessary cookies to run this site, and analytics cookies to understand how it's used. See our Privacy Policy for details.
A GitHub-reviewed security advisory, not necessarily under active exploitation the way our CISA KEV advisories are, but a real, disclosed vulnerability in an open-source dependency.
Affected packages
Vulnerable: < 12.3.1
Patched in 12.3.1
Details
A non-admin user who can update their own shares can reassign a share's creator (user_created), role, item, and collection fields after the share is created. The update is authorized against the row as it existed before the change, and the resulting row is never revalidated, so these fields can be set to values the user would not be permitted to assign when creating a share. By reassigning both user_created and role to an administrator the share's effective permissions get elevated.
This is a server-side authorization gap in the share update path. It does not by itself produce an administrator token. It re-opens a previously patched privilege-escalation surface on the effective permissions of a share.
directus_shares. This is not part of the baseline app-access grant, which is read-only on a user's own shares, but it is part of the recommended defaults permission template for directus_shares that instances commonly apply so the share feature is usable.The recommended default permission for updating directus_shares selects rows where the caller is the creator and permits writes to the full field set, including the creator, role, item, and collection. The ownership filter is evaluated only against the row as it exists before the update, so an owned share passes the check. The merged row is never re-checked to decide whether the caller may assign the new values.
Two guards that are enforced when a share is created are absent on update. On create, the creator is forced to the acting user, and a share-access check is run against the target item to confirm the caller is allowed to share it. On update, the supplied creator value is stored as given and no equivalent share-access check is run against the new item or collection, so both the creator and the shared target can be repointed to values the caller was never authorized to set. The read-only marking on the creator field in the schema is a Data Studio UI hint and does not constrain writes through the API.
When a guest authenticates through the share, Directus derives one accountability from the share's creator and another from the share's role, and applies administrator reach only when both resolve to an administrator. After both fields are reassigned to an administrator, both inputs resolve to administrator and the share is evaluated with full-schema reach starting from the shared item. This is the bypass of the CVE-2025-24353 intersection, which assumed the creator and selected role remain trustworthy after creation, when in fact both are mutable together through update.
Improper authorization (CWE-863) and improper privilege management (CWE-269). A non-admin can raise the effective permissions of a share they own beyond both their own permissions and the share role's permissions, exposing data reachable from the shared item that neither principal should be able to expose. The direct impact is to confidentiality. This issue alone does not grant write or availability impact.
More npm advisories
Talk to us about this
Find out whether this dependency (or others like it) is actually reachable in your codebase.
Get help patching, or building dependency-scanning into your pipeline going forward.
A secure code review or supply chain review finds this before an advisory does.