SQL Injection in github.com/daptin/daptin (CVE-2026-44349)
Summary
SQL injection in github.com/daptin/daptin (CVE-2026-44349). Risk of unauthorized operations or information disclosure. Exploitable via GET /api/. Mitigation: upgrade to 0.11.5 or later.
Original description
The description as published by the source.
Daptin is a GraphQL/JSON-API headless CMS. Prior to version 0.11.5, processFuzzySearch in server/resource/resource_findallpaginated.go:1484 splits the user-supplied column parameter by comma and interpolates each segment directly into goqu.L(fmt.Sprintf("LOWER(%s) LIKE ?", prefix+col)) raw SQL with no column whitelist check. The entry point is GET /api/ with operator=fuzzy (or fuzzy_any, fuzzy_all). Any authenticated user — including one who self-registered with no admin involvement — can read the entire database. This issue has been patched in version 0.11.5.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44349 has been found in github.com/daptin/daptin.
Attackers can target a specific entry point like GET /api/ over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/daptin/daptin to 0.11.5 or later.
If unsure, ask your IT team or search "github.com/daptin/daptin CVE-2026-44349" on the vendor's site.
CVE-2026-44349 (github.com/daptin/daptin) — CWE-89
Attack surface: GET /api/ / processFuzzySearch / column / fuzzy_any
Patched: 0.11.5 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SQL injection (CWE-89) exists in github.com/daptin/daptin. Attackers reach the vulnerable code path via GET /api/.
Check the vendor advisory for the affected versions of github.com/daptin/daptin. Attack surface: GET /api/ / processFuzzySearch / column / fuzzy_any.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.11.5.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /api/ requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/daptin/daptin' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/daptin/daptin' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/daptin/daptinを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /api/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /api/への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade github.com/daptin/daptin to 0.11.5ステージング環境で 0.11.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /api/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com