Skip to content
Fencer Vulns
medium 6.8

CVE-2026-52888 json

NocoBase: Sensitive Data Exposure via SQL Blacklist Bypass

published 2026-07-15 3 mo ago modified 2026-07-28 3 mo ago also GHSA-v8vm-cqh8-q87q , EUVD-2026-44800

cvss
6.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 40%
public exploits
0
none known

Summary

NocoBase is an AI-powered no-code/low-code platform for building business applications and enterprise solutions. In 2.0.59 and earlier, NocoBase @nocobase/plugin-collection-sql used the checkSQL() function in packages/plugins/@nocobase/plugin-collection-sql/src/server/utils.ts with an incomplete keyword blacklist that did not restrict PostgreSQL system catalog tables such as pg_shadow, pg_roles, and pg_stat_activity, allowing an admin-role user to read password hashes and database metadata through the SQL Collection feature. This vulnerability is fixed in 2.1.0-alpha.46.

Patch / fix

  • npm @nocobase/plugin-collection-sql 2.0.62, 2.1.0-alpha.46, 2.1.0-beta.45

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
3 mo ago

Exploit prediction

0.47% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/nocobase/nocobase/security/advisories/GHSA-v8vm-cqh8-q87q referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 6.8 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N
GitHub 3.1 6.8 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
npm @nocobase/plugin-collection-sql
<2.0.62
>=2.1.0-alpha.1, <2.1.0-alpha.46
>=2.1.0-beta.1, <2.1.0-beta.45
2.0.62
2.1.0-alpha.46
2.1.0-beta.45

Affected products

  • nocobase nocobase

Classification

Weakness
  • CWE-184 Incomplete List of Disallowed Inputs
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

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.