Summary
Capgo contains an authentication bypass in its account deletion endpoint, where accounts can be deleted without password re-authentication or secondary verification.
If an attacker hijacks a session, exploits CSRF, or tampers with request parameters, they can trigger unauthorized account deletion leading to data loss and denial-of-service.
Affected context
This vulnerability appears in Capgo deployments where sensitive account lifecycle actions, such as deletion, are protected only by an existing authenticated session.
It becomes risky in environments that rely on long-lived sessions, lack re-authentication for destructive actions, or do not enforce strong CSRF protections and integrity checks on critical endpoints.
Exploit preconditions
- Attack surface: Web or API-based account deletion endpoint accessible to authenticated users
- Required access: Valid user session (obtained legitimately, via hijacking, or through CSRF-induced requests) and ability to craft or intercept deletion requests
- Trigger point: Invocation of the account deletion endpoint without additional verification steps (e.g., password prompt, 2FA, or action-specific confirmation)
- Why exploitation is possible: The backend treats possession of a session as sufficient authorization for account deletion and fails to enforce robust re-authentication or request integrity checks
Why this happens
The underlying issue is insufficient authorization enforcement on a highly sensitive operation, mapping to CWE-306: Missing Authentication for Critical Function.
The account deletion endpoint relies solely on an existing authenticated session and does not perform additional verification such as password re-entry, multi-factor checks, or explicit high-friction confirmation.
As a result, any party that can drive the victim's browser, hijack their session, or manipulate request parameters can invoke account deletion without demonstrating legitimate control of the account at the time of the action.
Potential impact
- Accounts may be deleted without the owner's consent.
- Users could experience permanent or significant data loss.
- Services can suffer user-level denial-of-service through targeted deletions.
- Attackers may perform mass account removal in compromised environments.
- Loss of user trust and reputational damage for the service provider.
General mitigation guidance
Effective mitigation focuses on strengthening authorization for critical functions and reducing trust in ambient session state.
Common secure patterns include:
- Requiring password re-authentication or step-up authentication (e.g., MFA) before account deletion.
- Implementing explicit, high-friction confirmation flows (confirm dialogs, out-of-band verification, email or device confirmation) for destructive actions.
- Enforcing strong CSRF protections, including anti-CSRF tokens bound to user sessions and same-site cookie attributes.
- Applying fine-grained authorization checks that treat account deletion as a privileged operation with stricter controls than routine actions.
- Designing APIs with clear separation between low-risk and high-risk endpoints, with policy safeguards on high-risk operations.
How teams detect issues like this
Detection generally involves a mix of design review, code inspection, and automated policy checks:
- During code review, flag endpoints that perform destructive or irreversible actions (delete, disable, reset) and verify they enforce step-up authentication or robust confirmation.
- Use static analysis or linters configured to detect critical operations lacking CSRF checks, secondary verification, or explicit authorization policies.
- Implement architectural security reviews that catalogue critical functions and ensure they are covered by standardized access control patterns.
- Employ runtime monitoring and logging to track unusual patterns of account deletion and feed alerts into security operations for investigation.

