Cross-Site Scripting (XSS) in nocodb (CVE-2026-47383)
Summary
Cross-site scripting in nocodb (CVE-2026-47383). Risk of unauthorized operations or information disclosure. Exploitable via localStorage. Mitigation: upgrade to 2026.05.1 or later.
Original description
The description as published by the source.
NocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, an authenticated commenter could store HTML in row comments that executed as script when other users hovered over the comment in the expanded form view. The comment write paths persisted the raw comment body with no server-side sanitisation; the expanded-form sidebar then rendered the stored body and fed its data-tooltip attribute to Tippy with allowHTML: true. Even when the editor stripped script tags at write time, attribute-level payloads re-entered the DOM as live HTML on hover. This vulnerability is fixed in 2026.05.1.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-47383 has been found in nocodb.
Attackers can target a specific entry point like localStorage over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade nocodb to 2026.05.1 or later.
If unsure, ask your IT team or search "nocodb CVE-2026-47383" on the vendor's site.
CVE-2026-47383 (nocodb) — CWE-79
Attack surface: localStorage
Patched: 2026.05.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Cross-site scripting (XSS) (CWE-79) exists in nocodb. Attackers reach the vulnerable code path via localStorage.
Check the vendor advisory for the affected versions of nocodb. Attack surface: localStorage.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2026.05.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'nocodb' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'nocodb' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
nocodbを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade nocodb to 2026.05.1ステージング環境で 2026.05.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com