CVE-2026-129239 in Directusinfo

Summary

by MITRE • 11/16/2026

Directus is a real-time API and App dashboard for managing SQL database content. Prior to 12.3.1, Directus allows an authenticated non-admin with update permission on directus_shares to modify user_created, role, item, and collection on an existing owned share because authorization checks the pre-update row and does not revalidate the merged row. The update path does not force user_created to the acting user or rerun share access checks when item or collection changes. Setting user_created and role to administrator identifiers causes guest share authentication to derive administrator accountability from both fields, exposing data reachable from the shared item beyond the owner and share role permissions. The issue requires update permission on directus_shares, an item the account can share, and knowledge of administrator user and role identifiers, and it does not issue an administrator token or provide write or availability impact. This issue is fixed in version 12.3.1.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Analysis

by VulDB Data Team • 11/16/2026

The vulnerability identified in Directus versions prior to 12.3.1 represents a critical authorization bypass within the platform's share management subsystem, specifically affecting authenticated non-administrator users who possess update permissions on directus_shares entities. This flaw stems from an insufficient validation mechanism during the data modification process for existing shares owned by the attacker. When a user attempts to modify attributes of a shared item, such as changing the associated item or collection, the system performs authorization checks solely against the pre-update state of the row rather than revalidating permissions after the proposed changes are merged with the current database record. This architectural oversight allows an attacker to manipulate critical metadata fields including user_created and role without triggering appropriate access control restrictions that would normally apply if these fields were set correctly during initial creation or through proper administrative channels.

The technical core of this vulnerability lies in the failure to enforce referential integrity and identity consistency within the share object model. Specifically, when an attacker updates a share they own, the system does not force the user_created field to reflect the acting authenticated user nor does it re-evaluate share access controls if the item or collection references are altered. By manually setting the user_created and role fields to identifiers corresponding to an administrator account, the attacker exploits how Directus derives accountability for guest shares. The application logic incorrectly associates administrative privileges with these metadata fields during authentication checks for shared content. Consequently, a non-administrator can effectively masquerade as having higher-level permissions by manipulating these specific database columns, thereby bypassing the intended role-based access control boundaries that separate standard users from administrators.

The operational impact of this vulnerability is primarily focused on unauthorized data exposure rather than system compromise or availability disruption. An attacker leveraging this flaw can gain read access to sensitive information contained within shared items and collections that are normally restricted to administrative roles or specific high-privilege user groups. This means that confidential business logic, proprietary datasets, or personally identifiable information stored in the SQL database backend becomes accessible to unauthorized parties through the compromised share link mechanism. It is important to note that this vulnerability does not result in arbitrary code execution, privilege escalation to full administrator tokens, write access beyond the scope of shared items, or denial-of-service conditions. The attack vector requires specific prerequisites including valid authentication credentials for a non-admin account with update rights on shares, knowledge of existing share identifiers, and awareness of internal administrative user and role IDs within the target instance.

From a classification perspective, this vulnerability aligns closely with CWE-269 Improper Privilege Management due to the elevation of access privileges through metadata manipulation rather than traditional privilege escalation techniques. It also maps to ATT&CK technique T1078 Valid Accounts as it relies on legitimate but insufficiently validated credentials and permissions within the application framework. The root cause is fundamentally a CWE-264 Permissions, Privileges, and Access Controls issue where the security context is not properly maintained across state changes in persistent storage objects. To mitigate this risk, organizations must immediately upgrade to Directus version 12.3.1 or later which implements rigorous re-validation of authorization contexts post-update operations. Additionally, defensive measures should include enforcing strict write restrictions on metadata fields like user_created and role at the database level using triggers or constraints that prevent non-administrative users from modifying these attributes directly. Regular audits of share configurations and monitoring for anomalous changes to shared item ownership can further reduce exposure while patching is applied.

Responsible

GitHub M

Reservation

11/13/2026

Disclosure

11/16/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Want to know what is going to be exploited?

We predict KEV entries!