A server-side authorization gap exists in the share update path. An authenticated non-admin user with update permissions on `directus shares` can modify the `user created`, `role`, `item`, and `collection` fields of an existing share they own. This occurs because the system validates authorization based on the row's state before the update and fails to revalidate the merged row after the changes are applied. Consequently, the update process does not force the `user created` field to the acting user nor does it rerun share access checks when the `item` or `collection` is changed.
By reassigning both `user created` and `role` to administrator identifiers, a user can elevate the share's effective permissions. When a guest authenticates via such a share, the system derives administrator accountability from both fields, allowing access to data reachable from the shared item that exceeds the owner's and the share role's intended permissions. This issue impacts confidentiality but does not provide an administrator token or grant write or availability impact.