How severe is GHSA-45rp-9p97-h852?

No CVSS score has been assigned to GHSA-45rp-9p97-h852 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-45rp-9p97-h852?

GHSA-45rp-9p97-h852 affects the following packages: nocodb (npm). Ecosystems affected: npm.

How do I fix GHSA-45rp-9p97-h852?

Update nocodb to 0.301.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-45rp-9p97-h852 is resolved across your whole dependency graph.

How do I detect GHSA-45rp-9p97-h852 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nocodb. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-45rp-9p97-h852 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-45rp-9p97-h852?

O3 pinpoints whether GHSA-45rp-9p97-h852 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-45rp-9p97-h852 actively exploited in the wild?

No public exploit code has been indexed for GHSA-45rp-9p97-h852 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-45rp-9p97-h852?

GHSA-45rp-9p97-h852 is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-45rp-9p97-h852 published, and has it been updated?

GHSA-45rp-9p97-h852 was published on March 3, 2026 and was last updated on March 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-45rp-9p97-h852

GHSA-45rp-9p97-h852 is a SQL Injection vulnerability in nocodb. O3 Security confirms whether GHSA-45rp-9p97-h852 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

NocoDB Vulnerable to SQL Injection via DATEADD Formula

Also known asCVE-2026-28399

Published

Mar 3, 2026

Updated

Mar 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

nocodbnpm

2Kdownloads / week

Description

Summary

An authenticated user with Creator role can inject arbitrary SQL via the DATEADD formula's unit parameter.

Details

The third argument (unit) of DATEADD was interpolated directly into knex.raw() queries after only stripping quote characters. Validation in formulas.ts only checked Literal AST node types — non-Literal types bypassed validation entirely. Affected MySQL, PostgreSQL, and SQLite function mappings.

Impact

SQL injection allowing data exfiltration or modification, scoped to the connected database.

Credit

This issue was reported by @q1uf3ng.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`nocodb`	all versions	0.301.3

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nocodb. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update nocodb to 0.301.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-45rp-9p97-h852 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-45rp-9p97-h852 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-45rp-9p97-h852. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary An authenticated user with Creator role can inject arbitrary SQL via the DATEADD formula's unit parameter. ### Details The third argument (unit) of `DATEADD` was interpolated directly into `knex.raw()` queries after only stripping quote characters. Validation in `formulas.ts` only checked `Literal` AST node types — non-Literal types bypassed validation entirely. Affected MySQL, PostgreSQL, and SQLite function mappings. ### Impact SQL injection allowing data exfiltration or modification, scoped to the connected database. ### Credit This issue was reported by [@q1uf3ng](https://gi

O3 Security · Impact-Aware SCA

Is GHSA-45rp-9p97-h852 in your dependencies?

O3 detects GHSA-45rp-9p97-h852 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works