dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-47375

MEDIUM · 6.0 CVSS v3.1 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 →
66/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.04.1, an authenticated user with columnAdd permission on a Postgres-backed base can inject arbitrary SQL into the formula engine via the optional direction argument of ARRAYSORT(...). The value is unrestricted by formula validation and embedded into a knex.raw ORDER BY clause, executing during column creation and on every subsequent record read of the formula column. The vulnerability is specific to the Postgres mapping for ARRAYSORT in packages/nocodb/src/db/functionMappings/pg.ts. This vulnerability is fixed in 2026.04.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

Authenticated SQL injection in NocoDB's ARRAYSORT function for Postgres databases. The optional direction argument is not validated and gets directly embedded into a knex.raw ORDER BY clause during column creation and on every record read of the formula column, allowing arbitrary SQL execution.

MitigationUpgrade to NocoDB version 2026.04.1 or later. If immediate upgrade is not feasible, restrict or revoke columnAdd permission for Postgres-backed bases until the patch can be applied.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
High

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

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. Verify NocoDB version
    Check the running NocoDB instance version (typically accessible via the UI footer, API endpoint, or container image tag). Compare against the fixed version 2026.04.1.
    Affected if The installed version is earlier than 2026.04.1.
  2. Identify database backend
    Determine which database NocoDB is using as its underlying storage. This can typically be found in the NocoDB configuration file, environment variables (NC_DB), or the UI database settings.
    Affected if Postgres is the configured database backend.
  3. Locate ARRAYSORT formula columns
    Inspect the base schema for any columns created using the ARRAYSORT function in formula expressions. This can be done by examining column definitions via NocoDB API or UI column configuration panels.
    Affected if Any formula column uses the ARRAYSORT function with a direction argument.
  4. Review columnAdd permission
    Check user or role permissions for the affected bases to determine if columnAdd or columnEdit permissions are granted. This is typically found in the workspace/user management settings or via API endpoints for role permissions.
    Affected if Users have columnAdd or columnEdit permissions on Postgres-backed bases containing ARRAYSORT formula columns.

A user is affected if their NocoDB version is earlier than 2026.04.1, they use Postgres as the database, and they have ARRAYSORT formula columns with users who possess columnAdd permissions.

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.04.1 or later. If immediate upgrade is not feasible, restrict or revoke columnAdd permission for Postgres-backed bases until the patch can be applied.

Recommended fix High confidence

2026.04.1

  1. 1. Identify the current NocoDB version in use
  2. 2. Plan for upgrade during a maintenance window
  3. 3. Back up the existing NocoDB database and configuration
  4. 4. Upgrade NocoDB to version 2026.04.1 or later
  5. 5. Verify the upgrade was successful
  6. 6. Test that ARRAYSORT function works correctly on Postgres-backed bases
  7. 7. Confirm the SQL injection vulnerability is no longer present

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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