Summary
An authenticated user with Creator role can inject arbitrary SQL via the DATEADD formula's unit parameter.
Details
The third argument (unit) of DATEADD was interpolated directly into knex.raw() queries after only stripping quote characters. Validation in formulas.ts only checked Literal AST node types, non-Literal types bypassed validation entirely. Affected MySQL, PostgreSQL, and SQLite function mappings.
Credit
This issue was reported by @q1uf3ng.
Impact
SQL injection allowing data exfiltration or modification, scoped to the connected database.
Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-28399? CVE-2026-28399 is a medium-severity SQL injection vulnerability in nocodb (npm), affecting versions <= 0.301.2. It is fixed in 0.301.3. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
- Which versions of nocodb are affected by CVE-2026-28399? nocodb (npm) versions <= 0.301.2 is affected.
- Is there a fix for CVE-2026-28399? Yes. CVE-2026-28399 is fixed in 0.301.3. Upgrade to this version or later.
- Is CVE-2026-28399 exploitable, and should I be worried? Whether CVE-2026-28399 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-28399 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-28399? Upgrade
nocodbto 0.301.3 or later.