nocodb SQL Injection vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.5 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N

EPSS

• CVE-2023-43794: 0.87% estimated exploitation activity in the next 30 days; percentile 58.96 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary Nocodb contains SQL injection vulnerability, that allows an authenticated attacker with creator access to query the underlying database. Product nocodb/nocodb Tested Version 0.109.2 Details SQL injection in SqliteClient.ts (GHSL-2023-141) By supplying a specially crafted payload to the given below parameter and endpoint, an attacker can inject arbitrary SQL queries to be executed. Since this is a blind SQL injections, an attacker may need to use time-based payloads which would include a function to delay execution for a given number of seconds. The response time indicates, whether the result of the query execution was true or false. Depending on the result, the HTTP response will be returned after a given number of seconds, indicating TRUE, or immediately, indicating FALSE. In that way, an attacker can reveal the data present in the database. The triggerList method creates a SQL query using the user-controlled tablename parameter value from the tableCreate endpoint. Impact…

Published by the source

17 Oct 2023, 13:52 UTC

Last modified by the source

10 Sep 2026, 03:49 UTC

Source last checked

26 Oct 2026, 12:27 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-3m5q-q39v-xf8f

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-3m5q-q39v-xf8f

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-43794

Advisory: nocodb SQL Injection vulnerability
IDs: CVE-2023-43794, GHSA-3m5q-q39v-xf8f
Record: https://patchnext.com/advisories/cve-2023-43794 (revision 2, source checked 26 Oct 2026, 12:27 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: nocodb 0.111.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm nocodb: affected < 0.111.0; fixed in 0.111.0

## Suggested inspection (read-only)
- `npm ls nocodb --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on nocodb.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-3m5q-q39v-xf8f (OSV record GHSA-3m5q-q39v-xf8f lists affected ranges: npm nocodb >=0 <0.111.0 (fixed))
- Verified: https://github.com/advisories/GHSA-3m5q-q39v-xf8f (GitHub-reviewed advisory GHSA-3m5q-q39v-xf8f lists affected ranges: npm nocodb >=0 <0.111.0)

Commands are suggestions: review each one before running it.