Capgo (capgo.app) 未能限制通过 Supabase PostgREST 暴露的 表的直接写入访问权限。持有普通 Capgo 完整 API 密钥的用户可以插入一行记录,设置 和 ,从而绕过预期的后端 SSO 配置路径( )及其相关控制机制,包括:企业版套餐要求、通过 Supabase Management API 创建 SSO 提供商、DNS TXT 域名所有权验证、从 → → 的状态流转,以及由 Supabase Auth 签发的受信提供商 ID。 这条伪造的记录会被 SSO 发现与强制逻辑所信任,
Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
| # | POC Description | Source Link | Shenlong Link |
|---|
No public POC found.
Login to generate AI POC| CVE-2026-88862 | 8.8 HIGH | Capgo API Key Manager Authentication Bypass via x-limited-key-id |
| CVE-2026-88861 | 8.3 HIGH | Capgo AAL1 Session MFA Bypass via Direct RBAC Authorization |
| CVE-2026-88863 | 8.1 HIGH | capgo.app through 12.207.1 Privilege Escalation via invite_new_user_to_org |
| CVE-2026-88860 | 6.3 MEDIUM | Capgo Authorization Bypass via Stale Channel Permission Overrides |
No comments yet