CVE-2026-56283
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 html injection vulnerability in the organization settings endpoint that allows attackers to inject malicious HTML content. Attackers can craft payloads in the organization name field to redirect users to untrusted websites, enabling phishing attacks and reputational damage.
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 contains an HTML injection vulnerability in the organization settings endpoint. The organization name field accepts and renders user-supplied input without proper sanitization, allowing attackers to inject malicious HTML that can redirect users to untrusted external websites for phishing attacks.
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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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.
-
Check your Capgo versionLocate the Capgo application or package.json and identify the installed version number. Common methods: check package.json, run 'capgo --version' or 'npm list capgo', or look in the application admin panel under About/Version info.Affected if The installed version is lower than 12.128.2 (e.g., 12.128.1, 12.128.0, or any version before 12.128.2).
-
Verify access to organization settingsLog into Capgo and navigate to the organization settings or profile section where the organization name can be viewed or edited. This is typically found under Settings > Organization or a similar admin area.Affected if You have access to modify the organization name field - the vulnerability requires an authenticated user with permission to change organization settings.
-
Inspect the organization name field for HTML injectionView the current organization name as rendered in the UI (not just the input field). If you can edit it, temporarily enter a test string containing HTML such as '<script>alert(1)</script>' or '<a href="http://example.com">link</a>' and save, then view how it renders.Affected if The organization name is displayed with unescaped HTML tags in the rendered page (you see the actual tags or the script executes, rather than seeing the tags as plain text).
-
Check for suspicious redirectsExamine the Capgo application UI and URLs after loading the organization settings page. Look for any unexpected redirect parameters, unfamiliar external links, or if the browser URL changes to an untrusted domain when interacting with the organization name field.Affected if The application redirects you to an external untrusted website when the organization name is rendered, indicating the injection is being exploited.
You are affected if your Capgo version is below 12.128.2 AND you have access to modify the organization name field which renders unescaped HTML when displayed.
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 version 12.128.2 or later. In the meantime, implement output encoding/sanitization on the organization name field when rendered in HTML contexts to prevent injection of malicious HTML or JavaScript.
Capgo 12.128.2 or later
- 1. Identify the current version of Capgo being used in your environment
- 2. Review organization settings for any suspicious or malicious HTML content in the organization name field
- 3. Upgrade Capgo to version 12.128.2 or later
- 4. After upgrading, verify the fix by attempting to inject HTML in the organization name field to confirm the vulnerability is patched
- 5. Monitor for any signs of phishing or redirected users that may have been affected prior to patching
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-56283 — 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-56283 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