Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify Drogon app exposing filter input
-
DeliveryCraft malicious filter argument value
-
ExploitInjected SQL passes through makeCriteria into query
-
ExecutionBackend database executes attacker SQL
-
ImpactRead or modify database records
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Input neutralization, injection prevention
|
| Exploitation Conditions | Exploitation requires a Drogon-based application (versions up to 1.9.13) that passes attacker-controllable input into the ORM Criteria 'filter' argument handled by makeCriteria without parameterization or sanitization. This is a library-level footgun: the framework itself is only exploitable through an application code path that forwards untrusted input into ORM criteria, so applications that use parameterized values or never expose the filter argument to user input are NOT vulnerable. Where such a path exists and is reachable over the network, no authentication or user interaction is needed. Limiting factors: the required unsafe usage pattern is application-specific and non-universal, no official patch exists (vendor unresponsive), and exploitation is over the network against whatever endpoint exposes the filter. |
| Impact | This is a moderate-risk SQL injection in the Drogon C++ web framework's ORM layer (makeCriteria in Criteria.cc), best characterized as a library footgun rather than a turnkey remote exploit. The vendor CVSS 4.0 vector (5.5) rates AV:N/AC:L/PR:N/UI:N with all impacts Low (VC:L/VI:L/VA:L), and E:P confirms a proof-of-concept exists. Signals conflict: SSVC 'exploitation' is at Proof-of-Concept (POC published on GitHub gist), there is no EPSS score and no CISA KEV listing, so this is 'publicly available exploit code exists' - NOT active exploitation. The AC:L/PR:N framing overstates real-world reachability: the flaw is only exploitable if the consuming application routes untrusted, attacker-controlled input directly into the Criteria filter argument, which is a per-application coding decision, so realistic attack complexity is higher (AC:H) and many deployments are simply not vulnerable. Conversely, the all-Low impact rating likely understates a successful injection: SQLi against an ORM typically yields full database read (VC:H). Net: not an urgent internet-wide priority, but a real defect that matters for any Drogon app that passes user input into ORM filters. Vendor did not respond to disclosure, so no official patch is confirmed at time of analysis. |
| Exploit ScenarioDerived | A public PoC (GitHub gist by researcher 2H-K) demonstrates the injection. In a Drogon-based application that passes user-supplied input (e.g., a search/filter query parameter) into the ORM Criteria filter argument, a remote attacker submits a crafted filter value that breaks out of the intended predicate and injects arbitrary SQL, reading or tampering with database contents. Exploitation requires no authentication where the vulnerable endpoint is exposed, but only works if the application actually forwards untrusted input into makeCriteria without sanitization. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 21, 2026
SQL injection in Drogon (drogonframework drogon) up to version 1.9.13 allows remote attackers to manipulate the ORM filter argument in makeCriteria (orm_lib/src/Criteria.cc), potentially reading or altering database contents. Exploitation requires a Drogon-based application that forwards attacker-controllable input into the ORM Criteria filter without parameterization; applications that do not expose this argument to user input are not vulnerable. Publicly available exploit code exists, no vendor patch has been released, and the vendor did not respond to disclosure.
RemediationAI
No vendor-released patch has been identified; the vendor was contacted but did not respond. As a compensating control, avoid passing untrusted input directly to the ORM filter argument in makeCriteria; use allowlist validation or parameterized query constructs if the ORM supports them. If the filter must accept user input, sanitize or escape it before constructing criteria, or refactor the application to use prepared statements. Restricting network access to endpoints that expose the filter parameter can reduce exposure but may break functionality. Monitor the VulDB entry (https://vuldb.com/vuln/408059) and the Drogon repository for future patches. Applying a local patch to sanitize the filter in makeCriteria is possible but requires maintaining a forked version.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Drogon is a C++ web framework with an integrated ORM layer. The vulnerable function makeCriteria in orm_lib/src/Criteria.cc constructs SQL query criteria from a filter argument. Because the filter is not properly neutralized (CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component), an attacker who can control the filter string can inject arbitrary SQL. This is a library-level issue: the framework itself is only exploitable when an application passes untrusted input to the ORM filter. The affected versions are up to 1.9.13; no CPE strings were provided in the input data.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
AC:H because exploitation depends on the app routing untrusted input into the Criteria filter; PR:N as no auth is inherent; C:H reflects realistic SQLi database read, with modest integrity and no availability impact.
Primary rating from Vendor (vuldb).
CVSS VectorVendor: vuldb
DescriptionCVE.org
A flaw has been found in drogonframework drogon up to 1.9.13. This affects the function makeCriteria in the library orm_lib/src/Criteria.cc of the component ORM. Executing a manipulation of the argument filter can lead to sql injection. The attack may be performed from remote. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
EUVD-2026-83842
GHSA-c6jr-7xqv-9vjv
NVD
CVE.org
EPSS
VulDB
Exploit-DB