dbcve.org
CWE-384Weakness · CWE-384

CVE-2026-56224

MEDIUM · 5.4 CVSS v3.1 Published 2026-06-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges 8 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 console.capgo.app/login before 12.128.2 accepts access_token and refresh_token in URL query parameters, automatically authenticating users without confirmation. Attackers can craft malicious links to force victims into attacker-controlled sessions, exposing tokens in browser history and logs.

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

The Capgo console login endpoint before version 12.128.2 accepts access_token and refresh_token as URL query parameters, automatically authenticating users without requiring password or confirmation. This allows attackers to craft malicious links that force victims into attacker-controlled sessions while exposing sensitive tokens in browser history, server logs, and referrer headers.

MitigationUpgrade to Capgo console version 12.128.2 or later, which removes token support from URL parameters. Additionally, invalidate any tokens that may have been exposed and rotate credentials as a precautionary measure.

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
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Confirm Capgo console is accessible
    Identify if the Capgo console application is running in your environment. Check network accessible endpoints, container names, or service definitions for 'capgo' or 'console' references.
    Affected if Capgo console is deployed and accessible in your environment.
  2. Determine the installed Capgo console version
    Query the running Capgo console instance for its version information. This may be available via: 1) API endpoint like /version or /health, 2) Container/service metadata labels, 3) Package.json or similar version file if source is available, 4) Admin panel about page.
    Affected if The installed version is below 12.128.2.
  3. Test login endpoint with token URL parameters
    Craft a login request including access_token or refresh_token as URL query parameters to the Capgo console login endpoint (typically /login or /auth/login). Observe whether the user is authenticated without password entry.
    Affected if The login endpoint accepts and honors tokens passed as URL query parameters, authenticating the user automatically.
  4. Inspect server logs for token exposure
    Review Capgo console server access logs, application logs, and any proxy/load balancer logs. Search for URL patterns containing 'access_token' or 'refresh_token' in the query string.
    Affected if Tokens appear in URL query parameters within logs, indicating the vulnerability is active.

You are affected if your Capgo console version is below 12.128.2 and the login endpoint accepts authentication tokens via URL query parameters.

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 console version 12.128.2 or later, which removes token support from URL parameters. Additionally, invalidate any tokens that may have been exposed and rotate credentials as a precautionary measure.

Recommended fix Moderate confidence

12.128.2 or later

  1. 1. Check the current version of Capgo console (console.capgo.app) being used in your environment
  2. 2. Upgrade the Capgo console to version 12.128.2 or later to remediate the session fixation vulnerability
  3. 3. After upgrading, verify that the login page no longer accepts access_token and refresh_token as query parameters
  4. 4. Confirm that users must now go through the standard interactive login flow rather than being automatically authenticated via URL parameters
  5. 5. Review browser history and server logs to ensure no previously exposed tokens remain accessible

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-56224 — 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-56224 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