dbcve.org
CWE-602Weakness · CWE-602

CVE-2026-56256

HIGH · 7.1 CVSS v3.1 Published 2026-06-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/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 enforces mandatory two-factor authentication only at the UI level. Sensitive Organization (ORG) management API endpoints (e.g., editing organization details, inviting users) do not validate 2FA completion on the backend. An authenticated Admin user who has not enabled 2FA can replay or modify a previously captured ORG API request to perform privileged organization actions, bypassing the globally enforced 2FA requirement.

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 enforces mandatory 2FA only at the UI level while the backend Organization management API endpoints (editing org details, inviting users) fail to validate 2FA completion. An authenticated Admin without 2FA enabled can replay or modify captured API requests to perform privileged organization actions, bypassing the UI-enforced 2FA requirement.

MitigationImplement backend validation of 2FA completion status on all sensitive Organization management API endpoints and upgrade to Capgo version 12.128.2 or later.

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
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/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. Check Capgo version
    Locate the installed Capgo version in your application settings, package.json, or about page. Compare it to the affected range: any version before 12.128.2 is vulnerable.
    Affected if The installed version is lower than 12.128.2
  2. Identify admin accounts and 2FA status
    In the Capgo admin panel, navigate to Organization settings or User management. Review each admin account to see if 2FA is enabled in their profile settings.
    Affected if Any admin account lacks 2FA enforcement while having API access
  3. Test API endpoint for 2FA bypass
    Using an authenticated admin session without 2FA completed, send a POST request to the organization details update endpoint or user invitation endpoint. Observe if the request succeeds without requiring 2FA token validation.
    Affected if The API request succeeds and performs the action without returning a 2FA challenge response
  4. Inspect API response headers
    Capture the HTTP response from a sensitive API call (org edit or user invite) made by a non-2FA-enabled admin. Check for any 2FA-required headers or status codes that should enforce 2FA but are missing.
    Affected if The API returns success (200/201) instead of a 2FA challenge (401 with 2FA-required flag)

You are affected if your Capgo version is below 12.128.2 AND you have admin accounts with API access that have not completed 2FA enrollment, allowing them to bypass 2FA via the backend API.

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 backend validation of 2FA completion status on all sensitive Organization management API endpoints and upgrade to Capgo version 12.128.2 or later.

Recommended fix Moderate confidence

12.128.2 or later

  1. 1. Identify all Capgo instances running versions before 12.128.2
  2. 2. Review the Capgo 12.128.2 release notes or changelog to confirm the 2FA bypass fix details
  3. 3. Schedule a maintenance window for the upgrade
  4. 4. Backup the Capgo database and configuration files before proceeding
  5. 5. Upgrade Capgo to version 12.128.2 or later (preferably the latest stable release)
  6. 6. After upgrade, verify that organization management API endpoints now properly enforce 2FA validation on the backend
  7. 7. Review admin user accounts to ensure 2FA is enabled as required

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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