dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2026-56311

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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 authorization bypass vulnerability in the public.get_current_plan_max_org RPC function that allows unauthenticated attackers to retrieve arbitrary organization plan limits. Attackers can call the RPC endpoint with any organization UUID using only the public Supabase key to disclose billing information including MAU, bandwidth, storage, and build time limits for any organization.

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 12.128.2 has an authorization bypass in the public.get_current_plan_max_org RPC function. The function fails to validate that the caller has legitimate access to the requested organization, allowing any unauthenticated user with only the public Supabase key to retrieve billing plan limits (MAU, bandwidth, storage, build time) for ANY organization by supplying any UUID.

MitigationImplement proper authorization checks in the RPC function to verify the caller belongs to or has permission to access the requested organization. Also audit other public RPC functions for similar authorization bypasses.

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Verify Capgo version
    Check the installed Capgo version by reviewing your package.json, lock file, or deployment metadata. Compare the version number to 12.128.2 - any version before 12.128.2 is affected.
    Affected if The installed version is earlier than 12.128.2
  2. Identify the vulnerable RPC function
    Examine your Supabase database's RPC function definitions. Locate the public.get_current_plan_max_org function in the pg_proc system catalog or via the Supabase dashboard under Database > Functions.
    Affected if The public.get_current_plan_max_org RPC function exists in the database
  3. Test unauthorized organization access
    Using only the public Supabase key (found in your frontend configuration or capgo/settings), make an RPC call to public.get_current_plan_max_org with an arbitrary organization UUID: select * from public.get_current_plan_max_org(org_uuid: 'any-valid-uuid-here').
    Affected if The function returns billing plan data (MAU, bandwidth, storage, build time limits) for an organization you do not own or have access to
  4. Verify function lacks authorization logic
    Inspect the function definition by querying the prosrc column from pg_proc or viewing the function in Supabase dashboard. Look for any authorization checks (such as auth.uid() or verifying user organization membership).
    Affected if The function definition contains no authorization checks validating the caller belongs to or has permission to access the requested organization UUID

If you are running Capgo before version 12.128.2 and the public.get_current_plan_max_org function returns billing data for arbitrary organization UUIDs without authorization validation, your environment is affected by this CVE.

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

Implement proper authorization checks in the RPC function to verify the caller belongs to or has permission to access the requested organization. Also audit other public RPC functions for similar authorization bypasses.

Recommended fix Moderate confidence

Capgo version 12.128.2 or later

  1. 1. Identify the currently installed Capgo version in your environment
  2. 2. Upgrade Capgo to version 12.128.2 or later to remediate the authorization bypass vulnerability
  3. 3. Verify the upgrade was successful by checking the installed version
  4. 4. Confirm that the public.get_current_plan_max_org RPC function now properly enforces authorization checks

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
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-56311 — 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-56311 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