On this page (7 sections)
Daptin, an open-source GraphQL/JSON-API headless CMS written in Go, has a critical SQL injection flaw in versions up to and including 0.12.29. The bug sits in the generic list endpoint that every table exposes, and an attacker does not need an account to reach it. It is tracked as CVE-2026-77367 and fixed in 0.12.30.
If you run a Daptin instance that is reachable from the internet, or from a network you do not fully trust, plan an upgrade now. Only one independent publisher covers this story so far, and the details below come from the project's own advisory and the CVE record, so treat anything beyond those as unconfirmed.
What happened
The GitHub advisory says an unauthenticated attacker can inject SQL through the sort query parameter on the GET /api/{entity} list endpoint. Daptin creates this endpoint for every table in an instance, so the exposed surface is broad rather than limited to one feature.
The advisory lists the impact as ranging from denial of service, where a single crafted request makes the query fail with a server error, to blind or error-based extraction of data from tables the requester has no permission to read. The CVE record was published on 2026-11-19.
Technical details
The weakness class is SQL injection through identifiers. Most developers know to parameterize values, but column names in a SELECT list or ORDER BY clause cannot be bound as parameters, so code usually has to check them against a known list. Here that check was missing.
According to the advisory, the function PaginatedFindAllWithoutFilters in server/resource/resource_findallpaginated.go reads the sort values straight from the request. It then uses them to build both the selected columns and the ORDER BY clause through the goqu library's identifier constructor, without confirming that the column exists on the table. That constructor wraps the text in the dialect's quote character but does not escape an embedded quote of the same kind. An attacker-supplied quote therefore closes the identifier early, and the rest of the string is parsed as SQL.
The advisory also notes this is the same bug class as an earlier Daptin advisory, GHSA-rw2c-8rfq-gwfv, fixed in v0.11.4. That fix added a column allow-list check in the fuzzy-search code path, but the same validation was never applied to the base sort handling. The advisory points out that, unlike fuzzy search, plain sort is processed on every list request, authenticated or not.
Who is affected
- Any deployment of Daptin 0.12.29 or earlier, using the Go module github.com/daptin/daptin.
- Instances whose API is reachable from the internet or from untrusted internal networks. No account is needed to send the request.
- Instances holding sensitive data in tables that normal users cannot read. The advisory says data from such tables can be extracted through blind or error-based techniques.
- Teams that embed Daptin behind another application and assume the front end filters the query string. Check whether query parameters reach Daptin unchanged.
The practical risk is twofold. Any outsider who can reach the API can make individual queries fail, and a more patient one may be able to read data that permissions are supposed to protect. The advisory does not report any case of this being used against real systems.
How to check your exposure
First find out which version you run. Daptin is a single Go program, so the answer depends on how you deployed it. If you run it in a container, list the image tag. If you built it from source, check which release or commit you checked out.
This command lists running containers with their image names (run it on the Docker host). Look for a Daptin image and compare its tag with 0.12.30.
docker ps --format '{{.Names}}\t{{.Image}}'If your project uses Daptin as a Go dependency, this command prints the module version your build resolves (run it in the project directory). A version of 0.12.29 or lower is affected.
go list -m github.com/daptin/daptinYou can also look for evidence of probing. This read-only search prints requests whose query string contains a sort parameter with a backtick, written literally or percent-encoded as %60. Adjust the log path to your reverse proxy. Legitimate clients rarely send backticks, so any hit deserves a look.
grep -E 'sort=[^ &]*(%60|`)' /var/log/nginx/access.log | head -n 50Also watch for a cluster of HTTP 500 responses on /api/ list URLs from one source. The advisory says malformed sort values cause the query to fail with a 500 error, so a burst of those can indicate probing, though 500s have other causes too.
What to do now
- Identify every Daptin instance you run, including test and staging systems that share data with production.
- Upgrade to Daptin 0.12.30 or later. The fix is in the v0.12.30 release and in this commit.
- If you cannot upgrade immediately, limit who can reach the API: restrict it to trusted IP ranges or put it behind a VPN or authenticated proxy.
- Review proxy and application logs for unusual sort values and bursts of 500 errors on list endpoints, going back as far as your retention allows.
- If you find signs of probing and the instance held sensitive data, treat that data as potentially exposed. Rotate credentials, API keys and password hashes stored in Daptin tables as appropriate.
- Review which tables are readable by guests and remove access that is not needed.
- Rebuild and redeploy container images so they pull the patched release instead of a cached older layer.
Detection and monitoring afterwards
After patching, keep an eye on the API. Alert on spikes of 500 responses from list endpoints, and on query strings that contain quote characters or SQL punctuation. Keep access logs long enough to look back several weeks, since the issue has been described in public advisory data since at least the dates listed below.
From the outside, you can confirm your public endpoints still behave as expected with a security headers check and watch certificate and uptime changes through Webforta Monitor. These checks do not detect this flaw itself; they help you notice unexpected changes around the service.
Timeline
| Date | Event |
|---|---|
| Release v0.11.4 | Earlier, related SQL injection (GHSA-rw2c-8rfq-gwfv) fixed; a column allow-list was added in the fuzzy-search code path |
| Jul 12, 2026 | GitHub advisory shown as published in the daptin/daptin repository |
| Nov 19, 2026 | CVE-2026-77367 published by the National Vulnerability Database |
| Nov 20, 2026 | Published to and reviewed in the GitHub Advisory Database |
| Fixed version | Daptin 0.12.30 |
Only one independent publisher covers this story so far, so details here rest on the advisory and the CVE record. We do not claim confirmation beyond that.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
