dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-56214

HIGH · 7.5 CVSS v3.1 Published 2026-06-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Capgo before 12.128.2 contains an information disclosure vulnerability in Supabase PostgREST RPC endpoints is_trial_org and is_paying_org that allows unauthenticated attackers to enumerate organizations and disclose billing status using the public sb_publishable key. Attackers can invoke these endpoints to determine organization existence via distinguishable return values and identify paying customers for targeted profiling.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Capgo before version 12.128.2 exposes two Supabase PostgREST RPC endpoints (is_trial_org and is_paying_org) that lack proper authorization checks, allowing unauthenticated attackers to invoke them using only the public sb_publishable key. These endpoints return distinguishable values that reveal whether an organization exists and disclose its billing status, enabling enumeration of organizations and identification of paying customers.

MitigationUpgrade to Capgo version 12.128.2 or later to patch the vulnerable endpoints. Alternatively, implement proper authentication and authorization checks on these sensitive RPC functions to restrict access to authorized users only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check your Capgo version
    Review your package.json, lock file, or running Capgo server instance to identify the installed version number
    Affected if The version is lower than 12.128.2 (e.g., 12.128.1, 12.120.0, etc.)
  2. Confirm Supabase integration is in use
    Inspect your Capgo configuration files (such as app.config.ts, supabase.ts, or environment variables) for Supabase connection settings
    Affected if Supabase is configured and connected to Capgo
  3. Verify sb_publishable key exposure
    Locate your Supabase public publishable key in configuration files, environment variables, or client-side code
    Affected if The sb_publishable key is present and accessible in your environment
  4. Test endpoint accessibility
    Make an unauthenticated HTTP request to your Supabase PostgREST RPC endpoint for is_trial_org or is_paying_org using only the public key
    Affected if The endpoints respond with organization data or billing status without requiring authentication tokens beyond the public key
  5. Review API access logs
    Examine Supabase or application logs for any unauthenticated calls to rpc/is_trial_org or rpc/is_paying_org endpoints
    Affected if Such calls appear in logs without valid user authentication context

Your environment is affected if you run Capgo version below 12.128.2 with Supabase integration where the public sb_publishable key can invoke the is_trial_org or is_paying_org RPC endpoints without authorization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Capgo version 12.128.2 or later to patch the vulnerable endpoints. Alternatively, implement proper authentication and authorization checks on these sensitive RPC functions to restrict access to authorized users only.

Recommended fix High confidence

Capgo version 12.128.2 or later

  1. Upgrade Capgo to version 12.128.2 or later to remediate the information disclosure vulnerability
  2. Verify the upgrade was successful by checking the Capgo version
  3. Confirm that the Supabase PostgREST RPC endpoints `is_trial_org` and `is_paying_org` no longer expose organization existence or billing status to unauthenticated users

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-56214 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-56214 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data