dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-56221

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Cap-go before 12.128.2 contains multiple SQL injection vulnerabilities in cloudflare.ts where user-controlled values from API request bodies are interpolated directly into SQL query strings without sanitization or parameterization. Authenticated users with read-level API key permissions can inject arbitrary SQL through deviceIds, search, version_name, cursor, and actions parameters to access analytics data belonging to other users or applications.

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 confidence

SQL injection vulnerabilities in Cap-go cloudflare.ts where user-controlled API parameters (deviceIds, search, version_name, cursor, actions) are directly interpolated into SQL queries without parameterization. Authenticated users with read-level API key permissions can inject arbitrary SQL to access analytics data belonging to other users or applications.

MitigationUpgrade to Cap-go version 12.128.2 or later which addresses the SQL injection vulnerabilities. In the interim, implement input validation and convert all SQL queries to parameterized statements.

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Cap-go installation and version
    Run the following command to check the installed Cap-go version: npm list cap-go or check your package.json for the cap-go package version number.
    Affected if The installed version is lower than 12.128.2, indicating the SQL injection patches are not applied.
  2. Locate the cloudflare.ts module
    Search for the cloudflare.ts file in your project dependencies or node_modules directory. This is the module where the SQL injection vulnerability exists.
    Affected if The cloudflare.ts file is present and originates from a Cap-go version below 12.128.2.
  3. Verify API endpoints with vulnerable parameters are exposed
    Review your API routing configuration to confirm endpoints accepting deviceIds, search, version_name, cursor, or actions parameters are accessible. These are the user-controlled inputs that can be exploited for SQL injection.
    Affected if API endpoints accepting these parameters are exposed without additional authorization controls beyond basic read-level API key authentication.
  4. Confirm API key authentication is enabled
    Check your Cap-go configuration to determine if authenticated API key access is enabled. The vulnerability requires an authenticated user with read-level API key permissions.
    Affected if API key authentication is enabled and read-level keys can access the affected endpoints.

You are affected if Cap-go version is below 12.128.2, the cloudflare.ts module is in use, and API endpoints accepting deviceIds, search, version_name, cursor, or actions parameters are accessible to authenticated users with read-level API key permissions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Cap-go version 12.128.2 or later which addresses the SQL injection vulnerabilities. In the interim, implement input validation and convert all SQL queries to parameterized statements.

Recommended fix High confidence

Cap-go version 12.128.2 or later

  1. 1. Identify the current installed version of Cap-go in your environment
  2. 2. Backup your Cap-go configuration and any associated databases before upgrading
  3. 3. Upgrade Cap-go to version 12.128.2 or later
  4. 4. Verify the upgrade was successful by checking the installed version
  5. 5. Test that the application functions normally after the upgrade
  6. 6. Confirm the SQL injection vulnerability is remediated by reviewing the cloudflare.ts file for proper parameterization of deviceIds, search, version_name, cursor, and actions parameters

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-56221 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-56221 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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