CVE-2026-28359
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 · uneditedNocoDB is software for building databases as spreadsheets. Prior to version 0.301.3, an authenticated user with Editor role can inject arbitrary HTML into Rich Text cells by bypassing the TipTap editor and sending raw HTML via the API. This issue has been patched in version 0.301.3.
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 confidenceThis is a stored XSS vulnerability in NocoDB where authenticated users with Editor role can inject arbitrary HTML into Rich Text cells by bypassing the TipTap editor's sanitization and sending raw HTML directly through the API endpoint.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 0.301.3CVSS 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
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify NocoDB installation and versionCheck the package.json file in the NocoDB installation directory, or run 'npm list nocodb' if npm-installed. Check Docker container image tag if running via Docker.Affected if The installed version is below 0.301.3
-
Verify Editor role access existsReview user accounts in NocoDB admin panel under User Management to see if any users are assigned the Editor role.Affected if At least one user has Editor role permissions
-
Confirm Rich Text column usageInspect NocoDB project tables by accessing the schema or using API endpoint '/api/v1/db/meta/tables' to list columns and identify those with 'RichText' or 'ltar' type.Affected if Any table contains Rich Text type columns that are accessible to Editor role users
-
Review API request logs for raw HTMLExamine NocoDB server logs or API access logs for POST requests to '/api/v1/db/data' endpoints containing raw HTML tags such as <script>, <img onerror>, or <svg onload> in the body payload.Affected if Raw HTML tags are present in API request payloads to Rich Text fields
-
Check TipTap editor configurationInspect the Rich Text field configuration in NocoDB to confirm the TipTap editor is enabled as the default editor for Rich Text columns.Affected if TipTap editor is the active Rich Text editor and API accepts unsanitized input
You are affected if NocoDB version is below 0.301.3 AND your environment has Editor role users who can access Rich Text columns via API.
Generated from the published advisory. Verify against your own configuration.
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 · scoped0.301.3
Upgrade NocoDB to version 0.301.3 or later, which includes proper input sanitization for the API to prevent HTML injection.
0.301.3
- 1. Back up your existing Nocodb database and configuration
- 2. Upgrade Nocodb to version 0.301.3 or later
- 3. Verify the upgrade completed successfully
- 4. Test that the Rich Text cell functionality works correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28359 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-28359 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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