VulnerabilityPublished 28 Jul 2026

CVE-2026-52888: NocoBase · Sensitive Data Exposure via SQL Blacklist Bypass

Affects @nocobase/plugin-collection-sqlSource GCVE Database

Not known to be exploited · CVSS 6.8 Medium : upgrade to 2.0.62 when convenient.

Data as of 27 Oct 2026, 05:11 UTC

CVSS 3.1 base score

6.8Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.0.62, 2.1.0-alpha.46, 2.1.0-beta.45

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade @nocobase/plugin-collection-sql to 2.0.62; @nocobase/plugin-collection-sql to 2.1.0-alpha.46; @nocobase/plugin-collection-sql to 2.1.0-beta.45.

Affected software

Product	Affected	Fixed in
npm@nocobase/plugin-collection-sql	Affected <2.0.62	Fixed in 2.0.62
npm@nocobase/plugin-collection-sql	Affected >=2.1.0-alpha.1 <2.1.0-alpha.46	Fixed in 2.1.0-alpha.46
npm@nocobase/plugin-collection-sql	Affected >=2.1.0-beta.1 <2.1.0-beta.45	Fixed in 2.1.0-beta.45

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available for this vulnerability. Users should upgrade to version 2.0.62 or later where the issue is fixed. The vendor advisory confirms the availability of an official fix. Until patched, restricting admin role access to the SQL Collection feature or disabling it may reduce risk. The vendor recommends replacing the blacklist approach with an allowlist of permitted tables and schemas to prevent unauthorized data access.

Description

NocoBase plugin-collection-sql contains a vulnerability where its SQL blacklist filtering is incomplete, allowing authenticated admin users to bypass restrictions and access sensitive PostgreSQL system catalog tables and application user data. This enables exposure of password hashes and full database schema enumeration through the SQL Collection feature. The vulnerability arises from a keyword blacklist that fails to block access to critical system tables like pg_shadow and application tables such as users. A patch is available to address this issue.

Impact

An authenticated admin user can bypass the SQL blacklist and execute arbitrary SELECT queries on sensitive system catalog tables and application user tables. This leads to exposure of PostgreSQL password hashes, hashed user passwords stored in the application database, and full database schema information. The confidentiality of sensitive credential data is compromised, but there is no indication of integrity or availability impact. The CVSS score is 6.8 (medium severity) reflecting high confidentiality impact with low attack complexity and no user interaction required.

Summary

The checkSQL() function in NocoBase's plugin-collection-sql uses a keyword blacklist to prevent dangerous SQL queries but does not block access to sensitive PostgreSQL system catalog tables (e.g., pg_shadow, pg_roles, pg_stat_activity) or application tables containing user credentials. Authenticated users with admin privileges can exploit this to retrieve PostgreSQL password hashes, user credentials from the users table, and enumerate the database schema. The blacklist approach is fundamentally incomplete and can be bypassed. The correct mitigation is to implement an allowlist of permitted tables and schemas. The vulnerability affects versions prior to 2.0.62.

CWE-184Incomplete List of Disallowed Inputs (opens in a new tab)
Base weaknessOWASP Top 10 A03:2021: Injection (opens in a new tab)
The product implements a protection mechanism that relies on a list of inputs (or properties of inputs) that are not allowed by policy or otherwise require other action to neutralize before additional processing takes place, but the list is incomplete.
Implementation · Input Validation
Do not rely exclusively on detecting disallowed inputs. There are too many variants to encode a character, especially when different environments are used, so there is a high likelihood of missing some variants. Only use detection of disallowed inputs as a mechanism for detecting suspicious activity.
Attack patterns
Double Encoding (opens in a new tab)
Command Delimiters (opens in a new tab)
Flash Injection (opens in a new tab)
Using Leading 'Ghost' Character Sequences to Bypass Input Filters (opens in a new tab)
Exploiting Multiple Input Interpretation Layers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-200Exposure of Sensitive Information to an Unauthorized Actor (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #20OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Subverting Environment Variable Values (opens in a new tab)
ICMP Echo Request Ping (opens in a new tab)
TCP SYN Scan (opens in a new tab)
Enumerate Mail Exchange (MX) Records (opens in a new tab)
DNS Zone Transfers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 13 Sep 2026, 18:49 UTC

WeaknessesCWE-184, CWE-200

Technical details

References

Community reviews

Related threats