GHSA-f3qw-qg77-hmm4: IDOR in Organization Import Allows Unauthorized Data Injection
- Published:
- Fetched:
- Updated:
- Affects:
- dani-garcia vaultwarden
https://github.com/dani-garcia/vaultwarden/security/advisories/GHSA-f3qw-qg77-hmm4 ↗
IDOR in Organization Import Allows Unauthorized Data Injection Summary An Insecure Direct Object Reference (IDOR) vulnerability in the organization import endpoint allows an authenticated member with "Read-Only" permissions to bypass authorization checks and inject unauthorized cipher entries into a restricted collection. Details The vulnerability originates from an incorrect authorization check during the organization import process. When the system verifies whether a user can assign imported ciphers to an existing collection, it evaluates the user's visibility (read access) of the collection rather than their writability (manage/write access). Consequently, a user with strictly read-only access successfully passes this validation boundary. Furthermore, because the import payload explicitly supplies a list of target collections, a subsequent authorization check intended to verify cipher-level write access is short-circuited. This logical misalignment allows the read-only user's payload to be fully processed, establishing unauthorized relations in the database and mounting new cipher entries into the restricted collection. PoC General replication steps: Authenticate as a standard organization member who is granted strictly "Read-Only" access to a specific collection. Submit an HTTP POST request to the /api/ciphers/import-organization?organizationId= endpoint. Provide a structured JSON payload containing the target read-only collection's UUID in the collections array, and map a newly defined cipher entry to this collection using the relationships array. Observe that the server accepts the payload with an HTTP 200 OK status, successfully mounting the unauthorized cipher into the read-only collection. Impact This is an Improper Privilege Management flaw affecting multi-user organization vaults. No existing vault data is exposed. However, because every confirmed member holds the organization key, the injected entries can be valid, readable items (for example a login item pointing to an attacker-controlled URL) that other members with access to the collection will see and may trust. This flaw allows low-privileged accounts to inject unauthorized items into shared restricted collections. While these entries can be manually deleted by Organization Admins or Owners, the vulnerability leads to data pollution, UI clutter, and an unnecessary administrative burden to clean up the affected collections. Patches Fixed in 1.37.0. Assigning imported items to an existing collection now requires write access to that collection, and the collection list supplied in the import no longer short-circuits the cipher-level write check. ## Credits Reported independently by the following researchers, in order of first report: 1. @gigioneggiando (Luigi Colluto), 2026-07-08, as one item within a broader report, and again by email 2. @GN998, 2026-07-19, the complete standalone analysis this advisory tracks 3. @cipher-creator, Causal Security (https://causalsecurity.com/), by email Affected packages: rust:vaultwarden Patched: vaultwarden 1.37.0