2.7
Low
CVSS 3.1 base
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
To exploit it
What it gets
This page reproduces the published advisory for this finding. The advisory of record is linked above.
| Package | Ecosystem | Vulnerable | Fixed in |
|---|---|---|---|
nocodb | other | >= 0.253.0, < 2026.09.1 | 2026.09.1 |
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.
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.
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.
This issue was reported by @sfwani.
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.