# CVE-2026-112306: NocoBase plugin-collection-sql through 2.2.28 SQL Injection via sqlCollection:setFields

> Privileged users can inject SQL via the collection-sql plugin to read sensitive database information like password hashes.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-j67h-xf8r-r323

## What is CVE-2026-112306?

CVE-2026-112306 is a high-severity SQL injection vulnerability in nocobase, published on 19 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

NocoBase @nocobase/plugin-collection-sql through 2.2.28 contains an SQL injection vulnerability that allows privileged users to store unvalidated SQL by bypassing checkSQL() through the sqlCollection:setFields action. Attackers holding the collection-sql snippet can replace a benign collection query with dangerous statements executed on reload, reading pg_shadow password hashes or calling pg_read_file.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-112306?


## How do I fix CVE-2026-112306?

No fix has been published for CVE-2026-112306 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-112306 being exploited?

There is no known exploitation of CVE-2026-112306 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-112306 and fix it if it is affected.

What it is: CVE-2026-112306 is a high-severity SQL injection vulnerability in nocobase, published on 19 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-112306 in the wild and no public exploit code.

Affected product: nocobase. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-112306/ (Markdown: https://insights.sbomify.com/CVE-2026-112306/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-112306
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-112306
- OSV: https://osv.dev/vulnerability/CVE-2026-112306

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-112306/
Summaries are generated and may contain mistakes; the official description above is the record.