dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-47383

HIGH · 7.4 CVSS v4.0 Published 2026-06-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a stored XSS vulnerability in NocoDB's row comment system. Authenticated commenters could inject malicious HTML/JavaScript into comments that executed when other users hovered over them in the expanded form view. The vulnerability resulted from lack of server-side sanitization combined with Tippy.js tooltip rendering using allowHTML:true, allowing attribute-level payloads to execute as live HTML on hover.

MitigationUpgrade to NocoDB version 2026.05.1 or later, which implements server-side sanitization of comment content before storage and rendering.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
P
Scope
X

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify NocoDB version
    Log into the NocoDB interface and check the version number typically displayed in the footer of the application or in the admin settings. Alternatively, check the package.json file or Docker image tag if self-hosted.
    Affected if The installed version is earlier than 2026.05.1 (e.g., 2026.04.x, 2026.03.x, or any earlier release).
  2. Confirm row comment feature is in use
    Navigate to any table in NocoDB, open a record in expanded form view, and verify if the comment section is visible and accessible to authenticated users.
    Affected if The comment feature is enabled and users have the ability to post comments on records.
  3. Check for existing malicious comments
    Review recent comments in the database or through the UI for suspicious content such as HTML tags, javascript: URIs, event handlers (onmouseover, onerror, onclick), or unfamiliar external links.
    Affected if Any comment contains unescaped HTML, JavaScript, or attribute-level payloads that could execute on hover.

You are affected if your NocoDB version is earlier than 2026.05.1 and the row comment feature is accessible to authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to NocoDB version 2026.05.1 or later, which implements server-side sanitization of comment content before storage and rendering.

Recommended fix High confidence

2026.05.1

  1. Back up your NocoDB database before upgrading
  2. If using Docker, pull the new image: docker pull nocodb/nocodb:2026.05.1 or update your docker-compose.yml to use version 2026.05.1 and recreate containers
  3. If using npm, run: npm install [email protected]
  4. After upgrading, verify the version by checking the UI or API endpoint
  5. Test that comments function correctly after the upgrade
  6. Ensure any cached data or reverse proxy caches are cleared

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47383 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-47383 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data