CVE-2026-56308
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 · uneditedCapgo before 12.128.2 allows email address changes without requiring current password re-authentication or verification of the existing email address. An attacker with access to a valid session cookie or authenticated browser can change the account email to gain control of account recovery and bypass multi-factor authentication protections.
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 confidenceCapgo before 12.128.2 allows authenticated users to change their account email address without requiring password re-authentication or verification of the existing email address. An attacker with a valid session cookie can hijack account recovery by changing the email to one they control, thereby intercepting password reset links and bypassing multi-factor authentication protections.
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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Capgo installation and versionRun 'capgo --version' from CLI, check package.json version field, or inspect your deployed Capgo server/API headers to obtain the exact version numberAffected if Version is below 12.128.2 (e.g., 12.128.1, 12.127.x, or any earlier release)
-
Locate the email change interfaceLog into your Capgo account with valid credentials and navigate to Account Settings or Profile settings where email address can be modifiedAffected if The email change form is accessible without prompting for password re-entry or existing email verification
-
Test email change without re-authenticationAttempt to change your account email address to a different address without entering your current password or responding to a verification link sent to your existing emailAffected if The change succeeds using only an active session cookie, without any secondary authentication challenge
-
Confirm account recovery flow vulnerabilityAfter changing email, request a password reset and verify whether the reset link is sent to the new (attacker-controlled) email rather than requiring verification of email ownershipAffected if Password reset links can be redirected to an unverified email address that the user changed without authentication
-
Check if MFA protection is bypassedIf MFA is enabled on the account, change the email address and then attempt account recovery - observe whether MFA is circumvented because the recovery flow trusts the newly set emailAffected if MFA-protected accounts can be compromised by changing email without re-authentication, allowing the attacker to complete recovery without the original MFA factor
Your environment is affected if you run any Capgo version below 12.128.2 and the email change functionality accepts modifications without requiring password re-authentication or existing email verification.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade to Capgo version 12.128.2 or later, which implements proper authentication verification before allowing email address changes.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2026-56308 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-56308 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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