dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-47384

MEDIUM · 5.3 CVSS v4.0 Published 2026-06-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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
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.

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

SQL injection vulnerability in NocoDB's bulk groupBy endpoint allows authenticated users with column-create permission to inject arbitrary SQL by setting a column's title to a SQL fragment. The group-by.ts endpoint uses knex.raw() which directly interpolates the column_name into SQL strings, and the column lookup in data-table.service.ts matches on both the sanitized column_name and the free-text title field, enabling the allowlist bypass.

MitigationUpgrade to NocoDB version 2026.05.1 or later. If immediate upgrade is not possible, implement strict input validation on the title field to prevent SQL fragment injection and ensure column lookups do not rely on unsanitized free-text fields.

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
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Confirm NocoDB installation and version
    Locate the NocoDB instance and identify its version by checking package.json, docker image tag, or the /api/v1/version endpoint
    Affected if The installed version is lower than 2026.05.1 and the application uses the bulk groupBy endpoint functionality
  2. Verify column-create permission exists
    Check user roles and permissions in NocoDB admin panel or database to determine if the tested user has column-create permission
    Affected if Users with column-create permission can exploit this vulnerability
  3. Inspect group-by.ts endpoint logic
    Locate the group-by.ts file in the NocoDB source code and examine the knex.raw() call that interpolates column_name into SQL strings
    Affected if The code directly uses unescaped column_name in knex.raw() calls without proper parameterization
  4. Check data.table.service.ts column lookup
    Examine the column lookup function in data.table.service.ts to verify it matches on both the sanitized column_name and the free-text title field
    Affected if The lookup allows bypass of sanitization by matching on the title field which can contain injected SQL fragments
  5. Validate endpoint accessibility
    Confirm the /api/v1/db/bulk/groupBy endpoint is accessible and accepts column title parameters
    Affected if The bulk groupBy endpoint is exposed and accepts arbitrary column title values that reach the vulnerable code path

A NocoDB instance is affected if it is running a version prior to 2026.05.1 and allows authenticated users with column-create permission to access the bulk groupBy endpoint with column titles that can bypass sanitization through the title field lookup.

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 NocoDB version 2026.05.1 or later. If immediate upgrade is not possible, implement strict input validation on the title field to prevent SQL fragment injection and ensure column lookups do not rely on unsanitized free-text fields.

Recommended fix High confidence

2026.05.1

  1. 1. Backup your current NocoDB installation and database before upgrading.
  2. 2. Upgrade NocoDB to version 2026.05.1 or later.
  3. 3. Verify the upgrade was successful by checking the NocoDB version.
  4. 4. Test that the bulk groupBy functionality works correctly after the upgrade.
  5. 5. Confirm the SQL injection vulnerability is resolved by attempting the previously vulnerable action with a user that has column-create permissions.

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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