CVE-2026-56320
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 authorization flaw in POST /private/create_device that accepts a caller-supplied org_id parameter without validating it matches the target app's owner organization. Authenticated attackers can create device records for an application using a foreign organization identifier, bypassing the intended org/app authorization boundary.
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 has an authorization bypass in the POST /private/create_device endpoint. The API accepts a user-supplied org_id parameter without validating that it matches the target application's owner organization, allowing authenticated attackers to create device records in applications belonging to other organizations.
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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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 versionLocate the installed Capgo package or service and retrieve its version number. This may be via package.json, a running service banner, or the application's about/version endpoint.Affected if The installed version is earlier than 12.128.2
-
Verify API endpoint exposureConfirm that the POST /private/create_device endpoint is accessible in the Capgo deployment. Check API routing configuration or attempt a test request if authorized.Affected if The endpoint is exposed and accepts requests without additional authorization checks beyond authentication
-
Check org_id parameter handlingExamine how the create_device endpoint processes the org_id parameter. Review server-side code, API logs, or request handling logic to determine if the supplied org_id is validated against the authenticated user's organization or the target application's owner organization.Affected if The endpoint accepts any org_id value without validating ownership or organizational association
-
Test authorization boundaryIf authorized testing is permitted, send an authenticated request to /private/create_device with an org_id that differs from the authenticated user's organization to see if device creation succeeds for a different organization.Affected if Device records can be created for organizations other than the authenticated user's organization
A Capgo deployment is affected if it runs a version earlier than 12.128.2 and the /private/create_device endpoint accepts user-supplied org_id values without validating they match the target application's owner organization.
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 · scopedUpgrade to Capgo 12.128.2 or later, which includes proper org_id validation. Alternatively, implement server-side validation to ensure the provided org_id matches the authenticated user's organization or the target app's owner organization before processing the request.
12.128.2 or later
- Confirm current Capgo version in use
- Upgrade Capgo to version 12.128.2 or later to resolve the improper authorization vulnerability in POST /private/create_device
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-56320 — 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-56320 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