Executive brief
Capgo, a platform for managing app updates, contained a security flaw that allowed unauthorized access to sensitive user and organization data. By using a publicly available API key, an attacker could retrieve private information such as organization memberships, user roles, billing metadata, and management email addresses for any user. This could lead to the exposure of personally identifiable information (PII) and facilitate targeted social engineering or account takeover attempts.
Technical details
The vulnerability exists in the Supabase PostgREST RPC function 'public.get_orgs_v6(userid uuid)'. The function was configured as 'SECURITY DEFINER' and granted execution permissions to the 'anon' role, allowing unauthenticated access via the public publishable API key. Because the function failed to validate that the provided 'userid' matched the authenticated user's identity (or required a valid JWT), an attacker could perform an Insecure Direct Object Reference (IDOR) attack. By supplying an arbitrary user UUID to the POST /rest/v1/rpc/get_orgs_v6 endpoint, an attacker can retrieve organization memberships, roles, subscription/trial status, and the 'management_email' field. The issue is addressed in version 12.128.2 by restricting access to the function.
Affected products
- Capgo capgo < 12.128.2
Timeline
- 2026-03-03: advisory: GitHub Security Advisory published
- 2026-07-08: disclosed: NVD publication date