Sanaan Fayaz Wani

nocodb/nocodb

GHSA-jmgj-cq6g-6hr2

Incorrect Authorization via Base Member Removal

GHSA-jmgj-cq6g-6hr2

2.7

Low

CVSS 3.1 base

  1. 2026-09-24Reported privately
  2. 39 days later2026-11-02Published by the maintainer

What to do

If you run nocodb 0.253.0 to before 2026.09.1, upgrade to 2026.09.1 or later.

Anyone who can reach it over the network, with a high-privilege account and no user interaction, can change some data.Read from the CVSS 3.1 vector

CVSS 3.1 metrics

To exploit it

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None

What it gets

Confidentiality
None
Integrity
Low
Availability
None
Scope
Unchanged

Open this vector in the FIRST calculator ↗

Weakness
CWE-863 Incorrect Authorization
CVE
not assigned
Vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N
Also in nocodb
GHSA-jcc2-3vff-7867 6.5
2026-09-24Reported privately
39 days
2026-11-02Published by the maintainer

This page reproduces the published advisory for this finding. The advisory of record is linked above.

Affected versions

Package Ecosystem Vulnerable Fixed in
nocodb other >= 0.253.0, < 2026.09.1 2026.09.1

Summary

The check meant to stop a base member from removing someone with a higher base role never took effect, so a base Creator could remove an Owner of the base.

Details

baseUserDelete in base-users.service.ts, in both the Community and Enterprise services, compared the target’s role power with the caller’s through getProjectRolePower, which expects a user and reads its base_roles. The target side was given baseUser.base_roles, the roles themselves, so the helper found no roles on it and returned -1, and the comparison could never refuse the request. Base Creators hold the member removal permission, so a Creator could remove a member with the higher Owner role. The separate checks that keep the last Owner of a base and protect super admins were unaffected. The target user is now passed to the comparison, so removing a member whose role outranks the caller’s is refused.

Impact

An attacker needs an account with the Creator role on the base. They could remove another Owner of the base, a role above their own, as long as at least one Owner remained. Super admins and the base’s last Owner could not be removed this way.

Credit

This issue was reported by @sfwani.

The record

Weakness
CWE-863 Incorrect Authorization
Affected
nocodb 0.253.0 to before 2026.09.1
Fixed in
2026.09.1
Disclosure
2026-09-24 Reported privately
39 days later2026-11-02 Published
Advisory
GHSA-jmgj-cq6g-6hr2
Also in nocodb
GHSA-jcc2-3vff-7867 6.5

About this writeup

Sanaan Fayaz Wani (GitHub sfwani) reported this vulnerability to the nocodb maintainers under coordinated disclosure and is credited as a reporter in GHSA-jmgj-cq6g-6hr2, published 2026-11-02.

All published findings: advisory index.