CVE-2025-15439
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 · uneditedA vulnerability was identified in Daptin 0.10.3. Affected by this vulnerability is the function goqu.L of the file server/resource/resource_aggregate.go of the component Aggregate API. The manipulation of the argument column/group/order leads to sql injection. The attack may be initiated remotely. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.
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 · moderate confidenceDaptin 0.10.3 contains a SQL injection vulnerability in the Aggregate API function goqu.L within server/resource/resource_aggregate.go. The column, group, and order arguments passed to this function are not properly sanitized, allowing remote attackers to inject arbitrary SQL queries through these parameters.
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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Daptin is installedIdentify if Daptin is running in your environment by checking for the Daptin binary, Docker container, or process. Look for processes named 'daptin' or containers named 'daptin'.Affected if Daptin is present in your environment
-
Check Daptin versionRun 'daptin --version' or check the binary/container version tag. Compare against version 0.10.3.Affected if Running Daptin version 0.10.3
-
Confirm Aggregate API is accessibleIdentify if the /aggregate endpoint is exposed. Check your web server or API gateway configuration for routes accepting requests to paths like '/api/aggregate' or '/aggregate'. Review firewall rules and network ACLs.Affected if The Aggregate API endpoint is externally accessible without proper network segmentation
-
Check authentication configurationReview Daptin's configuration file (typically config.json) for 'enable_auth' or 'auth' settings. Verify whether the Aggregate API requires authentication by inspecting your authentication middleware or proxy settings.Affected if Authentication is disabled or not enforced on the Aggregate API endpoint
You are affected if Daptin version 0.10.3 is running with the Aggregate API endpoint accessible without proper input validation or authentication.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataImplement parameterized queries or proper input validation/sanitization for the column, group, and order arguments in the Aggregate API. If a patched version is available, upgrade to the fixed release.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-15439 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-15439 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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