Home/Research/Post

GHSA-66q9-mxf2-xqw6: TeamPass folder re-parenting authorization bypass

  • Severity: HIGH
  • CVE: CVE-2026-103035
  • Ecosystems: composer
  • Packages: nilsteampassnet/TeamPass

## Summary

Missing authorization in the update_folder action: any authenticated non-read-only user can rename, re-parent and convert to personal any folder in the instance, moving another team’s credential subtree into their own personal space and removing it from the organization. Confirmed at HEAD 2f271cdd (3.2.1.1), and present at 3.1.3.1 and 3.1.7.6.

## The defect

The folder-management endpoint dispatches an update_folder action that renames and re-parents a folder. Unlike its sibling actions in the same file, it never checks the edited folder id or the submitted parent id against the caller’s accessible-folder set, and the file itself performs no session/authorization gate at all. By pointing the new parent at their own personal folder, an authenticated low-privilege user takes ownership of any folder in the instance.

app/sources/folders.queries.php:
– The file never calls the session/authorization helpers: a grep for checkSession and userAccessPage across the whole file returns zero hits.
– case ‘update_folder’ (lines 294-662) contains no reference to the caller’s user-accessible_folders set. The only access-related logic is the personal-folder computation at lines 428-468 and the guard at line 503, which short-circuits on `(int) $isPersonal === 1`.
– The sibling actions do carry the check: case ‘add_folder’ validates against user-accessible_folders at line 743, case ‘delete_folders’ at line 904, and case ‘copy_folder’ applies the equivalent parent check.

So update…

Source: GitHub Security Advisories · 2026-11-20