dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2026-56239

HIGH · 7.6 CVSS v3.1 Published 2026-06-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable 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 a potential privilege escalation vulnerability in the public.apply_usage_overage SECURITY DEFINER function, which performs sensitive billing operations without enforcing internal authorization checks (no validation of auth.uid(), org membership, or check_min_rights). Because the function runs with the owner's privileges, it bypasses Row Level Security. If EXECUTE permission is available to the authenticated or anon roles (explicitly or via default privileges), an authenticated user could invoke it via Supabase RPC to manipulate billing data for arbitrary organizations, including unauthorized credit depletion and fraudulent overage event insertion.

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 a privilege escalation in the public.apply_usage_overage SECURITY DEFINER function which performs billing operations without validating auth.uid(), organization membership, or using check_min_rights. Because it runs with owner privileges and bypasses Row Level Security, an authenticated user with EXECUTE permission on the function (via authenticated or anon roles, explicitly or through defaults) can invoke it via Supabase RPC to manipulate billing data, deplete credits, or insert fraudulent overage events for any organization.

MitigationUpgrade to Capgo 12.128.2 or later, and revoke EXECUTE permission from authenticated/anon roles on public.apply_usage_overage if not already patched, ensuring the function validates user authorization before performing billing operations.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
Low

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

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. Identify Capgo version
    Query your Supabase database for the installed Capgo version. Typically found in a migrations table, settings table, or by checking the application metadata. Compare against 12.128.2.
    Affected if Installed version is before 12.128.2
  2. Verify apply_usage_overage function exists
    Query the database for the function: SELECT proname, pronamespace::regnamespace FROM pg_proc WHERE proname = 'apply_usage_overage';
    Affected if The function public.apply_usage_overage exists in the database
  3. Confirm function uses SECURITY DEFINER
    Check the function definition: SELECT prosrc FROM pg_proc WHERE proname = 'apply_usage_overage'; Look for SECURITY DEFINER in the function header or check pg_get_function_flags.
    Affected if The function is defined as SECURITY DEFINER (runs with owner privileges)
  4. Check EXECUTE permissions for vulnerable roles
    Query permissions: SELECT grantee, privilege_type FROM information_schema.function_privileges WHERE routine_name = 'apply_usage_overage'; Look for 'authenticated' or 'anon' roles with EXECUTE.
    Affected if The authenticated or anon role has EXECUTE permission on public.apply_usage_overage

User is affected if Capgo version is before 12.128.2 AND the public.apply_usage_overage SECURITY DEFINER function exists AND authenticated/anon roles have EXECUTE permission on it.

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 12.128.2 or later, and revoke EXECUTE permission from authenticated/anon roles on public.apply_usage_overage if not already patched, ensuring the function validates user authorization before performing billing operations.

Recommended fix High confidence

Capgo version 12.128.2

  1. Verify current Capgo version by checking the installed package version or application metadata
  2. Backup current database state and configuration before performing upgrade
  3. Upgrade Capgo to version 12.128.2 or later using the standard upgrade method for your deployment (npm, docker, or package manager)
  4. After upgrade, verify that the public.apply_usage_overage function no longer allows unauthorized invocation by confirming proper authorization checks are in place
  5. Confirm that SECURITY DEFINER function now validates auth.uid(), org membership, and check_min_rights before executing

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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