CVE-2026-56256
Received Received - Intake
Two-Factor Authentication Bypass in Capgo

Publication date: 2026-06-24

Last updated on: 2026-06-24

Assigner: VulnCheck

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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-24
Last Modified
2026-06-24
Generated
2026-06-24
AI Q&A
2026-06-24
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
capgo capgo to 12.128.2 (exc)
cap-go capgo to 12.128.2 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-602 The product is composed of a server that relies on the client to implement a mechanism that is intended to protect the server.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

CVE-2026-56256 is a vulnerability in Capgo versions before 12.128.2 where mandatory two-factor authentication (2FA) is enforced only at the user interface (UI) level but not on the backend for sensitive Organization management API endpoints.

This means that although the UI blocks access and prompts admins to enable 2FA, the backend does not verify if 2FA is completed when performing privileged actions such as editing organization details or inviting users.

An authenticated admin user who has not enabled 2FA can exploit this by capturing a valid API request and replaying or modifying it to bypass the 2FA requirement and perform unauthorized organization management actions.

Impact Analysis

This vulnerability can allow an attacker with admin credentials but without 2FA enabled to bypass the mandatory 2FA security control and perform privileged actions on the organization.

  • Unauthorized changes to organization details.
  • Inviting users without proper authentication.
  • Potential organizational takeover or policy violations due to unauthorized access.

Overall, it undermines the security posture by allowing privileged operations without the intended multi-factor authentication protection.

Detection Guidance

This vulnerability can be detected by monitoring and analyzing API requests to sensitive Organization Management endpoints, such as those for editing organization details or inviting users. Look for replayed or modified API requests from authenticated admin users who have not enabled two-factor authentication (2FA).

Commands or methods to detect this may include capturing and inspecting HTTP API traffic to identify repeated or suspicious requests that bypass 2FA enforcement. For example, using tools like tcpdump or Wireshark to capture network traffic, or employing API gateway logs to track requests to organization management endpoints.

  • Use tcpdump or tshark to capture API traffic: tcpdump -i <interface> -w capture.pcap port 443
  • Analyze captured traffic with Wireshark to identify repeated or modified organization management API requests.
  • Check server or API gateway logs for requests to sensitive endpoints from admin users without 2FA enabled.
  • Look for anomalies such as identical API requests replayed multiple times or requests that modify organization details without corresponding 2FA validation.
Mitigation Strategies

Immediate mitigation steps include enforcing server-side validation of two-factor authentication (2FA) status for all sensitive organization management API endpoints. This ensures that privileged actions cannot be performed unless 2FA is completed, regardless of frontend UI enforcement.

Additional recommended actions are:

  • Implement centralized authorization middleware that validates 2FA status on every privileged API request.
  • Invalidate previously issued tokens or sessions when 2FA becomes mandatory to prevent replay attacks using old credentials.
  • Log and monitor unauthorized access attempts to detect exploitation attempts.
  • Prompt all admin users to enable 2FA immediately and restrict access for those who have not done so.
Compliance Impact

This vulnerability allows an authenticated admin user to bypass mandatory two-factor authentication (2FA) on sensitive organization management API endpoints, enabling unauthorized privileged actions such as editing organization details or inviting users.

By undermining the enforcement of 2FA, a critical security control, the vulnerability increases the risk of unauthorized access and potential data breaches.

Such unauthorized access and potential data compromise can lead to non-compliance with common security standards and regulations like GDPR and HIPAA, which require strong access controls and protection of sensitive data.

Therefore, the vulnerability poses a risk to maintaining compliance with these regulations by failing to adequately enforce authentication controls on backend systems.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-56256. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart