dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2026-56252

MEDIUM · 5.4 CVSS v3.1 Published 2026-07-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click 5 weeks old

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 scope isolation vulnerability in the POST /webhooks/test endpoint that allows app-scoped API keys to invoke org-scoped webhook operations. Attackers with app-scoped credentials can trigger signed outbound webhook deliveries for arbitrary organization webhooks outside their declared app boundary, bypassing the limited_to_apps authorization check.

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 scope isolation flaw in the POST /webhooks/test endpoint where app-scoped API keys can bypass the limited_to_apps authorization check to trigger signed outbound webhook deliveries for org-scoped webhooks outside their declared app boundary.

MitigationUpgrade to Capgo version 12.128.2 or later which contains proper scope validation to enforce app/org boundary separation for webhook 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
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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. Identify Capgo installation version
    Check your Capgo installation or deployment for the installed version number. Common methods: check package.json if self-hosted, check the application dashboard version display, or query the API if accessible.
    Affected if The installed version is lower than 12.128.2 (e.g., 12.128.1, 12.127.x, earlier versions)
  2. Confirm access to POST /webhooks/test endpoint
    Verify that your Capgo deployment exposes the /webhooks/test endpoint. This is typically a webhook testing endpoint that allows sending test webhook payloads.
    Affected if The endpoint exists and accepts POST requests in your environment
  3. Identify app-scoped API keys in use
    Review your API key inventory or configuration to determine if any API keys are scoped to specific apps (app-scoped keys) rather than organization-wide (org-scoped keys). Check key metadata or permissions settings.
    Affected if You have API keys configured with app-level scope (limited_to_apps setting)
  4. Identify org-scoped webhooks
    Review your webhook configurations to find webhooks defined at the organization level (org-scoped webhooks) that are separate from app-specific webhooks.
    Affected if Org-scoped webhooks exist that differ from the app boundaries of your app-scoped API keys
  5. Verify authorization behavior
    Using an app-scoped API key with limited_to_apps restrictions, attempt to trigger the POST /webhooks/test endpoint to invoke an org-scoped webhook outside the declared app boundary. Observe whether the request succeeds despite the scope restriction.
    Affected if The app-scoped API key successfully triggers org-scoped webhooks that should be outside its authorized scope

Your environment is affected if you run Capgo version below 12.128.2 and have app-scoped API keys that can trigger org-scoped webhooks beyond their declared app boundaries through the /webhooks/test endpoint.

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 which contains proper scope validation to enforce app/org boundary separation for webhook operations.

Recommended fix High confidence

12.128.2 or later

  1. Identify the Capgo installation and confirm the current version is below 12.128.2
  2. Backup the current configuration and data
  3. Upgrade Capgo to version 12.128.2 or later
  4. Verify the upgrade was successful by checking the version number
  5. Test that app-scoped API keys can no longer invoke org-scoped webhook operations through the POST /webhooks/test endpoint

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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