dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-44349

HIGH · 7.1 CVSS v4.0 Published 2026-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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/<entity> 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in Daptin's fuzzy search functionality. The processFuzzySearch function in resource_findallpaginated.go directly interpolates user-supplied column parameters into raw SQL queries (LOWER(%s) LIKE ?) without validating against a column whitelist, allowing authenticated attackers to inject arbitrary SQL and read the entire database.

MitigationUpgrade to Daptin version 0.11.5 or later which includes a column whitelist check. As a temporary mitigation, disable the fuzzy, fuzzy_any, and fuzzy_all operators until patching is possible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Daptin version
    Run the daptin binary with version flag (e.g., ./daptin --version or check the binary metadata) and note the version number
    Affected if Version is below 0.11.5 (the fixed release)
  2. Verify fuzzy search endpoint availability
    Check if API endpoints responding to fuzzy, fuzzy_any, or fuzzy_all query parameters are accessible (typically on /api/{endpoint} routes with GET requests containing these operators)
    Affected if Fuzzy search operators are accepted without column validation errors and the Daptin version is below 0.11.5
  3. Inspect configuration for column whitelist
    Review Daptin configuration files (config*.json or world.json depending on setup) for any column whitelist settings related to search operations
    Affected if No column whitelist is configured and the version is vulnerable
  4. Confirm authenticated access is possible
    Verify that user accounts or API tokens exist in the Daptin deployment, as the CVE requires authenticated access to exploit
    Affected if User authentication is enabled and the Daptin version is below 0.11.5

The environment is affected if Daptin version is below 0.11.5 and the fuzzy search API endpoints (using fuzzy, fuzzy_any, or fuzzy_all operators) are accessible to authenticated users without column whitelist validation in place.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Daptin version 0.11.5 or later which includes a column whitelist check. As a temporary mitigation, disable the fuzzy, fuzzy_any, and fuzzy_all operators until patching is possible.

Recommended fix High confidence

0.11.5

  1. Check current Daptin version by running the binary with --version or checking the running container/image tag
  2. If using Go to run: Update the go.mod file to require version 0.11.5 or use 'go get github.com/daptin/[email protected]'
  3. If using Docker: Pull the updated image tag v0.11.5 (e.g., 'docker pull daptin/daptin:v0.11.5')
  4. If using a pre-built binary: Download the release binary for version 0.11.5 from the GitHub releases page
  5. Restart the Daptin service to apply the updated version
  6. Verify the version has been updated successfully

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,260
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,816.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44349 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44349 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data