CVE-2026-56312
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 contains an improper validation vulnerability in the accept_invitation endpoint that creates user accounts before captcha validation is enforced. Attackers can bypass captcha protection by sending POST requests with invalid captcha tokens to create unwanted accounts and burn invite links.
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 version 12.128.2 has an improper validation vulnerability in the accept_invitation endpoint where user account creation occurs before captcha validation is enforced. Attackers can bypass captcha protection by sending POST requests with invalid captcha tokens to create unauthorized accounts and consume invite links.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
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 versionCheck the installed Capgo version by inspecting package.json, version file, or running 'capgo --version' if CLI is available. Compare the version number to 12.128.2.Affected if Installed version is lower than 12.128.2
-
Verify accept_invitation endpoint is exposedReview application routing or API configuration to confirm the /accept_invitation endpoint is accessible. Check API routes or endpoint definitions.Affected if The accept_invitation endpoint is publicly accessible
-
Review captcha validation order in accept_invitationInspect the source code or logic flow of the accept_invitation endpoint. Trace the execution order to determine whether captcha validation occurs before or after user account creation logic.Affected if User account creation logic executes before captcha validation completes
-
Test captcha bypassSend a POST request to the accept_invitation endpoint with an invalid or missing captcha token and observe whether an account is created despite the invalid captcha.Affected if Account creation succeeds with invalid captcha token
A system is affected if it runs Capgo version lower than 12.128.2 and the accept_invitation endpoint creates user accounts before validating captcha tokens.
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.
dbcve · scopedMove captcha validation to occur BEFORE any account creation logic executes in the accept_invitation endpoint, rejecting invalid tokens before any user record is created.
12.128.2
- Identify the current Capgo version running in your environment
- Backup your current Capgo installation and database
- Upgrade Capgo to version 12.128.2 or later
- Verify the upgrade was successful by checking the version number
- Test the accept_invitation endpoint to confirm captcha validation is now enforced before account creation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-56312 — 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-56312 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