dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2026-56313

HIGH · 8.1 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 →
87/100
Remediation priority · High
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 cross-organization account disruption vulnerability in the SSO prelink endpoint that allows enterprise administrators to delete password identities of users in foreign organizations. Attackers with org.update_settings permission and an active SSO provider can call the prelink-users endpoint to permanently remove email-based authentication for any user matching the provider's email domain, forcing victims to use the attacker's SSO provider or complete password reset recovery.

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 broken access control vulnerability in the SSO prelink endpoint. Enterprise administrators with org.update_settings permission and an active SSO provider can call the prelink-users endpoint to delete password identities of users in other organizations, provided the SSO provider's email domain matches the victim's email address.

MitigationUpgrade to Capgo 12.128.2 or later. As a temporary measure, review and restrict org.update_settings permissions and audit SSO provider configurations to limit potential abuse.

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
None
Integrity
High
Availability
High

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

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 application version
    Locate the installed Capgo version in the application settings, about page, or package.json. Common locations: admin dashboard 'About' section, or running 'capgo --version' CLI command if available.
    Affected if Version is below 12.128.2 (e.g., 12.128.1, 12.127.x, or earlier)
  2. Verify SSO provider is configured
    Navigate to Enterprise settings > SSO or Identity provider configuration. Look for any active SSO provider (SAML, OIDC, or similar) that is enabled and operational.
    Affected if An SSO provider is enabled and configured with an email domain
  3. Identify users with org.update_settings permission
    Go to Enterprise admin roles or permissions management panel. List all administrators or roles that possess the 'org.update_settings' permission.
    Affected if Any user account holds the org.update_settings permission (this grants ability to call the prelink-users endpoint)
  4. Review SSO provider email domain settings
    In the SSO provider configuration, examine the configured email domains or allowed domains field that defines which user emails the SSO provider handles.
    Affected if SSO provider has email domains configured that could match users in other organizations

You are affected if your Capgo version is below 12.128.2 AND you have an active SSO provider configured with email domains AND at least one user has org.update_settings permission.

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. As a temporary measure, review and restrict org.update_settings permissions and audit SSO provider configurations to limit potential abuse.

Recommended fix Moderate confidence

Capgo version 12.128.2 or later

  1. Check current installed version of Capgo by reviewing package.json, package-lock.json, or the running application's version manifest
  2. Upgrade Capgo to version 12.128.2 or later by running the appropriate package manager update command (e.g., npm update @capgo/... or the specific Capgo package used in your installation)
  3. After upgrading, restart all Capgo services to ensure the new version is loaded
  4. Verify the upgrade was successful by confirming the new version number matches 12.128.2 or higher
  5. If using automated deployment, ensure the upgrade is reflected in your CI/CD pipeline and deployment logs

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 / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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