dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-56227

MEDIUM · 5.4 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 →
60/100
Remediation priority · Elevated
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 server-side request forgery vulnerability in webhook URL validation that allows loopback and internal addresses. Organization admins can configure webhooks pointing to localhost or 127.0.0.1, and when triggered, the backend performs outbound requests to these addresses with error responses disclosed to users.

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 · moderate confidence

Capgo before version 12.128.2 contains a server-side request forgery (SSRF) vulnerability in its webhook URL validation logic. The application fails to restrict webhook URLs from pointing to loopback addresses (localhost, 127.0.0.1), allowing organization admins to configure webhooks that trigger outbound requests to internal resources. Error responses from these internal requests are disclosed back to users, potentially revealing sensitive internal service information.

MitigationUpgrade to Capgo version 12.128.2 or later, which contains proper validation to reject loopback and internal addresses in webhook URLs. Until upgraded, network segmentation and monitoring can help limit exposure.

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. Determine your Capgo installation version
    Locate the Capgo application and check its installed version number. Common methods include viewing the application dashboard, checking package.json or similar metadata files, or querying the application's version endpoint if available.
    Affected if The installed version is lower than 12.128.2 (e.g., 12.128.1, 12.127.x, or earlier)
  2. Identify if webhooks are configured
    Navigate to the webhook configuration section in the Capgo admin interface or inspect the application's configuration database/tables for webhook entries. Look for records containing webhook URL definitions.
    Affected if Webhook functionality is enabled and webhook URL configurations exist in the system
  3. Inspect configured webhook URLs for loopback or internal addresses
    Review all configured webhook URLs and check if any contain localhost, 127.0.0.1, or other internal/private IP addresses (such as 10.x.x.x, 192.168.x.x, 172.16-31.x.x).
    Affected if At least one webhook URL is configured pointing to 127.0.0.1, localhost, or an internal IP range
  4. Verify webhook URL validation behavior
    Attempt to create or modify a webhook with a loopback URL (localhost or 127.0.0.1) and observe whether the application accepts or rejects it. If rejected, check the error message type.
    Affected if The application accepts webhook URLs pointing to loopback addresses without rejecting them

Your environment is affected if you are running Capgo version lower than 12.128.2 and the system allows configuring webhooks that point to localhost or internal addresses, which could enable SSRF attacks against internal resources.

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 validation to reject loopback and internal addresses in webhook URLs. Until upgraded, network segmentation and monitoring can help limit exposure.

Recommended fix High confidence

12.128.2

  1. Identify the current installed version of Capgo in your environment
  2. Upgrade Capgo to version 12.128.2 or later
  3. Verify the upgrade was successful by checking the Capgo version
  4. Review existing webhook configurations to ensure no localhost or internal address URLs are in use
  5. Test that webhook functionality works correctly with valid external URLs

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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