CVE-2022-2063 json
Improper Privilege Management in nocodb/nocodb
published 2022-06-13 4 y ago modified 2026-06-17 4 mo ago also GHSA-fq4h-m3c8-8m2v , EUVD-2022-6040
- cvss
- 9.0
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 72%
- public exploits
- 0
- none known
Summary
Improper Privilege Management in GitHub repository nocodb/nocodb prior to 0.91.7+.
Patch / fix
- npm nocodb 0.91.8
- nocodb nocodb/nocodb 0.91.7+
- github.com/nocodb/nocodb@269a19c commit
- github.com/nocodb/nocodb#2262 pull request
- github.com/nocodb/nocodb#2337 pull request
- huntr.dev/bounties/156f405b-21d6-4384-9bff-17ebfe484e20 advisory
Exploit prediction
1.39% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- huntr.dev https://huntr.dev/bounties/156f405b-21d6-4384-9bff-17ebfe484e20 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 9.0 | CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
| GitHub | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | nocodb | <0.91.8 |
0.91.8 |
Affected products
- nocodb nocodb/nocodb
Classification
- Weakness
-
- CWE-269 Improper Privilege Management
References
-
github.com
/nocodb/nocodb/commit/269a19c2ad89a0e8a7596498e3806ff2ec1040c2
web, patch, third-party-advisory
-
huntr.dev
/bounties/156f405b-21d6-4384-9bff-17ebfe484e20
web, exploit, patch, third-party-advisory
-
github.com
/nocodb/nocodb/pull/2262
web
-
github.com
/nocodb/nocodb/pull/2337
web
-
nvd.nist.gov
/vuln/detail/CVE-2022-2063
advisory
-
github.com
/nocodb/nocodb
package
Sources
- CVE List CVE-2022-2063
- GitHub Advisory GHSA-fq4h-m3c8-8m2v
- NVD CVE-2022-2063
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.