dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-41422

HIGH · 8.3 CVSS v3.1 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 →
89/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.4, the /aggregate/:typename endpoint accepted column and group query parameters that were passed verbatim to goqu.L() — a raw SQL literal expression builder — without any validation. This bypassed all parameterization and allowed authenticated users with any valid session to inject arbitrary SQL expressions. This issue has been patched in version 0.11.4.

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

Daptin CMS prior to 0.11.4 contains a SQL injection vulnerability in the /aggregate/:typename endpoint where column and group query parameters are passed directly to goqu.L() raw SQL literal builder without validation, bypassing parameterization and allowing authenticated users to inject arbitrary SQL expressions.

MitigationUpgrade to Daptin version 0.11.4 or later which implements proper input validation for the column and group parameters before passing them to the SQL builder.

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
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

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 CMS installation
    Locate the Daptin binary or running service - check common paths like /usr/local/bin/daptin, /opt/daptin, or running processes via 'ps aux | grep daptin'. Also check if running as a container via 'docker ps'.
    Affected if Daptin CMS is installed and running
  2. Determine installed Daptin version
    Run 'daptin --version' or check the version from the binary metadata. If running in Docker, check the image tag or run 'docker images' to identify the version.
    Affected if Version is prior to 0.11.4 (e.g., 0.11.3, 0.11.2, etc.)
  3. Verify /aggregate endpoint accessibility
    Check if the API server is exposed by reviewing reverse proxy configurations, firewall rules, or container port mappings. The endpoint /aggregate/:typename accepts query parameters.
    Affected if The Daptin API is network-accessible (even internally) and the /aggregate endpoint is reachable
  4. Confirm authentication configuration
    Review Daptin's configuration (config.yaml or environment variables) to determine if authentication is enabled. Check for 'authtoken' or 'auth' settings. Without authentication, the SQL injection requires valid user credentials.
    Affected if Authentication is enabled and users can access the /aggregate endpoint with valid credentials

You are affected if Daptin CMS versions prior to 0.11.4 are running with the /aggregate endpoint accessible to authenticated users.

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.4 or later which implements proper input validation for the column and group parameters before passing them to the SQL builder.

Recommended fix High confidence

0.11.4

  1. 1. Identify the currently running Daptin version by checking the binary or container image tag
  2. 2. If running a version prior to 0.11.4, plan for upgrade during a maintenance window
  3. 3. Download Daptin version 0.11.4 from the official releases (e.g., GitHub releases page)
  4. 4. Backup the existing Daptin installation, configuration files, and database
  5. 5. Stop the running Daptin service
  6. 6. Replace the Daptin binary or update the container image to version 0.11.4
  7. 7. Review any new configuration options or migration requirements in the release notes
  8. 8. Start the upgraded Daptin service
Caveat Review release notes for any configuration or API changes between your current version and 0.11.4

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41422 — 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-41422 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