Daptin: Unauthenticated SQL Injection in the `sort` Parameter Hits Every Entity List Endpoint (CVE-2026-77367)
What happened
A newly published GitHub Security Advisory (GHSA-hq2p-f2vj-v3cm, CVE-2026-77367, CVSS 9.4) reports an unauthenticated SQL injection vulnerability in Daptin. It affects the sort query parameter on GET /api/<entity>, the generic entity-list endpoint exposed by every table in a Daptin instance.
Per the advisory, PaginatedFindAllWithoutFilters in server/resource/resource_findallpaginated.go reads the sort parameter and passes each value to goqu's goqu.I() raw identifier constructor with no check that the referenced column exists on the table. Because goqu.I() does not escape an embedded backtick matching the dialect's quote character, an attacker-supplied backtick closes the identifier early and the rest of the string is parsed as SQL grammar rather than a literal column name. The advisory notes this is the same bug class previously fixed with an allow-list check in a sibling code path via GHSA-rw2c-8rfq-gwfv, but that fix was never applied to the base sort handling. A public PoC is included showing both error-based reflection and a backtick breakout, with no Authorization header required and default guest-readable tables such as world and user_account as targets.
Why it matters for defenders
This is reachable by any unauthenticated requester against any Daptin deployment using default or guest-readable entity permissions, with no prerequisite account or special configuration. Reported impact ranges from trivial denial of service (a single crafted request reliably returns a 500, as shown by the advisory's repeated-request PoC) up to blind and error-based extraction of data from tables the requester has no read permission for. Per the PoC, this includes columns such as password on user_account. Exploit status is listed as PoC-public, so weaponization risk should be treated as immediate for internet-facing Daptin instances.
What defenders should watch for now
- Inventory any Daptin deployments and check the running version against the fix once a patched release is published by the maintainers. The advisory does not yet state a fixed version.
- At the network or WAF layer, flag or block requests to
/api/*endpoints where thesortparameter contains backticks, SQL comment sequences (--), parentheses, or subquery keywords (select,union), consistent with the PoC payloads in the advisory. - Review application and database logs for repeated 500 errors on list endpoints with error text referencing
no such columnor SQL syntax errors naming thesortvalue. This matches the advisory's own PoC output. - Where feasible, restrict anonymous or guest read permissions on entity tables as a compensating control until a patch is applied, since the flaw is reachable without authentication specifically because default tables are guest-readable.
This is developing, net-new intel based directly on the GitHub Security Advisory. No fixed version or vendor response is confirmed in the source at time of writing. Full technical details and the proof-of-concept are available in the original advisory: GHSA-hq2p-f2vj-v3cm.