Daptin unauthenticated SQL injection in list sort parameter
Daptin versions before 0.12.30 are affected, reproduced on a fresh SQLite database with no custom schema using a backtick-quoting dialect build. Fixed in 0.12.30.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.12.30
- Who is exposed
- Not reported
Summary
Daptin, a headless CMS, has an SQL injection flaw in its generic list endpoint, which accepts attacker-controlled values in the sort parameter without checking them against the table schema. Remotely and without logging in, an attacker can use this to extract unauthorized table data or repeatedly trigger query failures.
Written by a model
Original description
Daptin is a GraphQL/JSON-API headless CMS. Prior to 0.12.30, the generic GET /api/{entity} list endpoint accepts attacker-controlled sort values in PaginatedFindAllWithoutFilters in server/resource/resource_findallpaginated.go without validating the requested column against the table schema. The code uses those values for SELECT and ORDER BY identifier construction, so an embedded identifier quote can terminate the quoted identifier and make the remainder parse as SQL, allowing an unauthenticated attacker to extract unauthorized table data through blind or error-based behavior or repeatedly trigger query failures. This issue is fixed in version 0.12.30.
What to do
Upgrade to a fixed version: 0.12.30.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-77367 (Daptin: Unauthenticated SQL Injection via the `sort` query parameter on every entity list endpoint), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-77367 (entry last updated 2026-11-19):
Affected:
- daptin daptin: fixed in 0.12.30
Fixed versions: 0.12.30.
Conditions (all must be true for the bug to be hit):
- Reproduced on a fresh SQLite database with no custom schema, using a backtick-quoting dialect build. (source: https://github.com/daptin/daptin/security/advisories/GHSA-hq2p-f2vj-v3cm)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-77367 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-77367 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/daptin/daptin/security/advisories/GHSA-hq2p-f2vj-v3cm
- https://github.com/daptin/daptin/commit/b0bcc1318832b9055781f032853ef9d2264652cf
- https://github.com/daptin/daptin/releases/tag/v0.12.30
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-77367
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-77367"}.Affected versions
- daptin daptinfixed in 0.12.30
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.4/10CVSS 9.4
- No patch0/5No signal
What would change the score
- Would score about 74 if added to CISA KEV
- Would score about 69 if CISA's SSVC rates exploitation active
- Would score about 34 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Evidence 5
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · daptin/daptin · Advisory GHSA-hq2p-f2vj-v3cm |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-77367 |
| Record | NVD · CVE-2026-77367 |
| Other links 2 | |
| Repository | GitHub · daptin/daptin · Commit b0bcc131 |
| Repository | GitHub · daptin/daptin · Release v0.12.30 |
Questions about CVE-2026-77367
Is CVE-2026-77367 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
An unauthenticated request can use the sort query parameter on entity list endpoints to inject SQL. This can cause query failures that deny service, and blind or error-based extraction of data from tables the requester has no permission to read.
Source: github.com
Which versions are affected by CVE-2026-77367?
daptin: before 0.12.30.
Source: cve.now feed data
Am I affected, and how do I check?
The product range covers Daptin versions before 0.12.30. The report reproduced the issue on a fresh SQLite database with no custom schema, using a backtick-quoting dialect build. Compare the installed Daptin version with 0.12.30 and check the database setup against those conditions.
Source: github.com
How do I fix CVE-2026-77367?
Upgrade Daptin to version 0.12.30 or later, which is the listed fixed version.
Source: github.com
Related
- CVE-2026-77369Daptin: Broken Access Control (IDOR) in the generic YJS collaboration endpoint
- CVE-2026-72575daptin - Authentication Bypass via Null Owner Permission Check on usergroup Objects
- CVE-2026-62160Daptin: ParseAcceptLanguage `_` separator bypass enables >250x CPU amplification via Accept-Language header in LanguageMiddleware
- CVE-2026-41422Daptin vulnerable to SQL injection via unvalidated goqu.L() calls in aggregate API
- CVE-2026-44349Daptin fuzzy search injects unvalidated column name into raw SQL
- CVE-2026-87977IBM Guardium Data Protection SQL Injection
No corrections so far. Something wrong on this page? Report an error.