Description
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.
Published: 2026-06-24
Score: 7.1 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

Capgo before 12.128.2 enforces mandatory two-factor authentication only at the UI level. Sensitive organization management API endpoints, such as editing organization details or inviting users, do not require verification of a completed 2FA challenge on the backend. As a result, an authenticated administrator who has not enabled 2FA can capture or replay a valid organization API request and modify it to perform privileged organization actions, effectively bypassing the globally enforced 2FA requirement. This flaw, a misdirected authentication check (CWE-602), allows the attacker to alter organization settings, invite new users, or otherwise influence privileged configuration without meeting the intended authentication controls.

Affected Systems

The affected product is Capgo, specifically any deployment running a version earlier than 12.128.2. No additional product or vendor variants are mentioned, so the scope is limited to that platform and its organization management API.

Risk and Exploitability

The CVSS score of 7.1 indicates a moderate to high severity vulnerability, although the EPSS score is not available, preventing accurate estimation of the current exploitation probability. The vulnerability is not listed in CISA’s KEV catalog, and no public exploitation evidence is reported. An attacker would need to first obtain valid admin credentials (or compromise them through social engineering or another vulnerability) and then replay or modify an organization API request. Because the flaw allows privileged actions to be performed without completing a 2FA step, the attack surface is confined to environments where administrators are not forced to use multi‑factor authentication, making the risk especially acute for organizations with lax 2FA enforcement on the backend.

Generated by OpenCVE AI on June 24, 2026 at 13:29 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade to Capgo 12.128.2 or newer, where the backend validates two‑factor authentication for organization‑management operations.
  • Enforce two‑factor authentication for all existing administrator accounts and verify that the backend consistently checks the 2FA status before processing org‑management API requests.
  • Revoke any organization API tokens that were captured or replayed, and audit recent organization‑management activity to detect unauthorized changes.

Generated by OpenCVE AI on June 24, 2026 at 13:29 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 24 Jun 2026 16:00:00 +0000

Type Values Removed Values Added
First Time appeared Cap-go
Cap-go cap-go
Vendors & Products Cap-go
Cap-go cap-go

Wed, 24 Jun 2026 14:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Wed, 24 Jun 2026 12:00:00 +0000

Type Values Removed Values Added
Description 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.
Title Capgo - Two-Factor Authentication Bypass via Organization Management API
Weaknesses CWE-602
References
Metrics cvssV3_1

{'score': 7.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N'}

cvssV4_0

{'score': 7.1, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-06-24T13:49:39.681Z

Reserved: 2026-06-19T21:56:09.656Z

Link: CVE-2026-56256

cve-icon Vulnrichment

Updated: 2026-06-24T13:49:03.223Z

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-06-24T15:45:06Z

Weaknesses
  • CWE-602

    Client-Side Enforcement of Server-Side Security