# CVE-2026-47384: NocoDB: SQL Injection via Column Title in Bulk GroupBy

> Authenticated users can inject SQL via column titles in bulk groupBy operations, allowing unauthorized database access or modification.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Jun 2026
- **Updated:** 24 Jun 2026
- **Also known as:** GHSA-p8wx-5f39-w3x4

## What is CVE-2026-47384?

CVE-2026-47384 is a medium-severity SQL injection vulnerability in nocodb, published on 23 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

NocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, an authenticated user with column-create permission can inject SQL into the bulk groupBy endpoint by setting a column's title to a SQL fragment. The bulk groupBy path in group-by.ts builds three database-specific knex.raw() aggregations that interpolate the request's column_name directly into the SQL string. Column lookup in data-table.service.ts matches on both the sanitized column_name field and the free-text title, so a title containing a SQL fragment bypasses the public endpoint's existing column allowlist and reaches the query builder unescaped. This vulnerability is fixed in 2026.05.1.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-47384?

2 open source packages ship an affected version, including nocodb.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nocodb` | npm | All versions | 2026.05.1 |
| `nocodb` | npm | All versions | 2026.05.1 |

## How do I fix CVE-2026-47384?

Upgrade nocodb to 2026.05.1 or later.

## Is CVE-2026-47384 being exploited?

There is no known exploitation of CVE-2026-47384 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47384 and fix it if it is affected.

What it is: CVE-2026-47384 is a medium-severity SQL injection vulnerability in nocodb, published on 23 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-47384 in the wild and no public exploit code.

Affected packages and fixed versions:
- nocodb (npm): affected all versions; fixed in 2026.05.1
- nocodb (npm): affected all versions; fixed in 2026.05.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47384/ (Markdown: https://insights.sbomify.com/CVE-2026-47384/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47384
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47384
- OSV: https://osv.dev/vulnerability/CVE-2026-47384

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47384/
Summaries are generated and may contain mistakes; the official description above is the record.