# CVE-2026-56281: Capgo - SQL Injection via Unvalidated limit Parameter in Admin Stats Endpoint

> An authenticated admin can inject SQL into the analytics endpoint to read data or cause denial of service.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jul 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-6ffx-8hjj-jhhf, GHSA-p2w3-hw46-3q2w

## What is CVE-2026-56281?

CVE-2026-56281 is a medium-severity SQL injection vulnerability in Capgo, published on 12 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Capgo before 12.128.2 contains a sql injection vulnerability in the POST /private/admin_stats endpoint where the limit parameter is destructured from unvalidated request body and interpolated directly into Cloudflare Analytics Engine SQL queries via template literals. An attacker with platform admin credentials can inject SQL fragments to enumerate dataset schemas, extract analytics data, or cause denial-of-service against the analytics backend.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-56281?


## How do I fix CVE-2026-56281?

No fix has been published for CVE-2026-56281 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-56281 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-56281 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-56281 and fix it if it is affected.

What it is: CVE-2026-56281 is a medium-severity SQL injection vulnerability in Capgo, published on 12 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-56281 exists.

Affected product: Capgo. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-56281/ (Markdown: https://insights.sbomify.com/CVE-2026-56281/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-56281
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-56281
- OSV: https://osv.dev/vulnerability/CVE-2026-56281

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-56281/
Summaries are generated and may contain mistakes; the official description above is the record.