Summary
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.
Details
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.
Credit
This issue was reported by @DavidCarliez. It was independently reported by @Mouhebbenelwafi.
Impact
Stored Cross-Site Scripting against any user who views the affected row. Script runs in
the NocoDB origin with the victim's session and can read the auth JWT fromlocalStorage. Authentication and comment permission are required.
Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-47383? CVE-2026-47383 is a high-severity cross-site scripting (XSS) vulnerability in nocodb (npm), affecting versions <= 2026.05.0. It is fixed in 2026.05.1. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
- Which versions of nocodb are affected by CVE-2026-47383? nocodb (npm) versions <= 2026.05.0 is affected.
- Is there a fix for CVE-2026-47383? Yes. CVE-2026-47383 is fixed in 2026.05.1. Upgrade to this version or later.
- Is CVE-2026-47383 exploitable, and should I be worried? Whether CVE-2026-47383 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-47383 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-47383? Upgrade
nocodbto 2026.05.1 or later.