dbcve.org
NocodbApplication

CVE-2026-28357

MEDIUM · 5.4 CVSS v3.1 Published 2026-03-02
Fix available
A fix is available. Upgrade to 0.301.3 or later.
See remediation →
58/100
Remediation priority · Elevated
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 version 0.301.3, a stored XSS vulnerability exists in the Formula virtual cell. Formula results containing URI::() patterns are rendered via v-html without sanitization, allowing injected HTML to execute. 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 confidence

A stored XSS vulnerability exists in NocoDB's Formula virtual cell feature. When formula results contain URI::() patterns, they are rendered via v-html without sanitization, allowing injected HTML to execute in users' browsers.

MitigationUpgrade to NocoDB version 0.301.3 or later which includes proper sanitization of formula result rendering.

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
NocodbApplication
Affected:< 0.301.3

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
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 checks

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

  1. Identify installed NocoDB version
    Access the NocoDB installation directory and check the package.json version field, or use the NocoDB UI by navigating to the Help menu or Settings > About. Alternatively, check via command line: nc or npm list nocodb if accessible.
    Affected if The installed version is lower than 0.301.3 (e.g., 0.301.2, 0.300.x, etc.)
  2. Confirm Formula virtual cell feature is in use
    In the NocoDB UI, navigate to any table and look for columns with the Formula type. You can also inspect the column configuration by accessing a column's edit menu to verify the field type is set to Formula.
    Affected if Formula columns exist in any database table within the NocoDB instance; the vulnerability applies specifically to this feature.
  3. Check for formulas using URI::() patterns
    Review existing Formula column configurations. Look for any formulas that include URI::() function calls, such as URI::encode(), URI::decode(), or similar URI-related functions. Inspect each formula column's formula expression.
    Affected if One or more Formula columns contain URI::() function calls in their expressions; these results would be rendered unsafely.
  4. Verify formula result rendering method
    Access the NocoDB frontend application files (if accessible) and locate the component handling Formula cell rendering. Search for v-html directive usage on formula output elements in the codebase.
    Affected if The formula results are rendered using v-html without prior sanitization, which is the vulnerable condition described in this CVE.

You are affected if your NocoDB version is below 0.301.3 and you have Formula columns using URI::() patterns rendered with v-html in your instance.

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
Upgrade available Upgrade to 0.301.3 or later
Fixed in 0.301.3
Interim mitigation

Upgrade to NocoDB version 0.301.3 or later which includes proper sanitization of formula result rendering.

Recommended fix High confidence

0.301.3 or later

  1. Upgrade Nocodb to version 0.301.3 or later to address the stored XSS vulnerability in the Formula virtual cell
  2. After upgrading, verify that Formula results containing URI::() patterns are no longer rendered unsafely via v-html
  3. Test the Formula virtual cell functionality to confirm the patch does not break legitimate use cases

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

Fix this in Nocodb Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-28357 — 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-28357 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