dbcve.org
CWE-184Weakness · CWE-184

CVE-2026-52888

MEDIUM · 6.8 CVSS v3.1 Published 2026-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable Zero-click 5 weeks old

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
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.

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 · moderate confidence

The NocoBase @nocobase/plugin-collection-sql plugin contains an incomplete SQL keyword blacklist in its checkSQL() function that fails to restrict PostgreSQL system catalog tables (pg_shadow, pg_roles, pg_stat_activity). This allows authenticated admin users to bypass the blacklist and query sensitive system metadata including password hashes.

MitigationUpgrade NocoBase to version 2.1.0-alpha.46 or later which implements a complete blacklist for PostgreSQL system catalog tables.

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
Changed
Confidentiality
High
Integrity
None
Availability
None

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

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. Identify plugin installation and version
    Run 'npm list @nocobase/plugin-collection-sql' in the NocoBase project directory to list the installed version of the collection-sql plugin
    Affected if The plugin version is installed but lower than 2.1.0-alpha.46 (or version cannot be determined and NocoBase core is below 2.1.0-alpha.46)
  2. Check NocoBase core version
    Run 'npm list @nocobase/core' or check the package.json file to determine the installed NocoBase core version
    Affected if The core version is below 2.1.0-alpha.46 and the collection-sql plugin is present
  3. Verify PostgreSQL is the database
    Check the NocoBase configuration file (typically .env or config/database.ts) for the DB_DIALECT or DB_TYPE setting set to 'postgres'
    Affected if The database dialect is PostgreSQL and the plugin is installed
  4. Confirm plugin is enabled
    Check the NocoBase configuration for plugin activation in the 'plugins' section of the config file, or query the /api/app:info endpoint if authenticated as admin
    Affected if The collection-sql plugin is listed as enabled in the configuration

A user is affected if the @nocobase/plugin-collection-sql plugin is installed and enabled, the database is PostgreSQL, and the NocoBase version is below 2.1.0-alpha.46 (or the plugin version is below the fixed release).

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 NocoBase to version 2.1.0-alpha.46 or later which implements a complete blacklist for PostgreSQL system catalog tables.

Recommended fix High confidence

2.1.0-alpha.46

  1. 1. Identify the NocoBase instance running version 2.0.59 or earlier that uses the @nocobase/plugin-collection-sql plugin
  2. 2. Consult the official NocoBase upgrade documentation at github.com/nocobase/nocobase for migration instructions from 2.0.x to 2.1.x
  3. 3. Upgrade the @nocobase/plugin-collection-sql plugin to version 2.1.0-alpha.46 or later
  4. 4. Verify the upgrade by checking that the checkSQL() function now properly restricts access to PostgreSQL system catalog tables (pg_shadow, pg_roles, pg_stat_activity)
  5. 5. Test the SQL Collection feature with an admin account to confirm password hashes and sensitive metadata are no longer accessible
Caveat Upgrading from 2.0.x to 2.1.0-alpha.46 involves a major version change; alpha releases may contain untested features and potential compatibility issues

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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