Unauthenticated organization and billing-status disclosure via RPCs
Published Jun 20, 2026 · Updated Jun 20, 2026
Information disclosure in Capgo before 12.128.2 allows remote attackers to enumerate organizations and read billing status via Supabase RPCs. The is_trial_org and is_paying_org PostgREST endpoints accept a public sb_publishable key and return distinguishable 0/null and true/false values for supplied organization IDs. No account is required; the client-exposed key and candidate organization IDs are sufficient to identify valid organizations and paying customers.
Summary
What happened
Information disclosure in Capgo before 12.128.2 allows remote attackers to enumerate organizations and read billing status via Supabase RPCs. The is_trial_org and is_paying_org PostgREST endpoints accept a public sb_publishable key and return distinguishable 0/null and true/false values for supplied organization IDs. No account is required; the client-exposed key and candidate organization IDs are sufficient to identify valid organizations and paying customers.
The record
- CVE
- CVE-2026-56214
- Published
- Jun 20, 2026
- Updated
- Jun 20, 2026
- Vendor
- Capgo
- Product
- Capgo
- Classifications
- CWE-200, CWE-203, T1591
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 20, 2026CVE publishedPublication date reported by the CVE source.
- Jun 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <12.128.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Vendor advisory RPC proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo