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

CVE-2026-47376

MEDIUM · 5.1 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 →
58/100
Remediation priority · Elevated
Remotely reachable No privileges

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.04.1, the password-reset page rendered the URL token directly into a JavaScript string literal in a server-rendered EJS template. EJS <%= %> HTML-entity-encodes a fixed set of characters but does not escape single quotes or backslashes, so a crafted token could break out of the JS string context and execute attacker-controlled script in the NocoDB origin. Triggering required only that a victim follow a malicious password-reset link. This vulnerability is fixed in 2026.04.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

NocoDB prior to 2026.04.1 has a stored XSS in the password-reset page where the reset token is rendered into a JavaScript string literal in a server-side EJS template. The `<%= %>` escaping only handles HTML entities but does not escape single quotes or backslashes, allowing attackers to break out of the JS string context and inject arbitrary JavaScript via a crafted token in a malicious password-reset link.

MitigationUpgrade to NocoDB version 2026.04.1 or later. Until then, users should not click on untrusted password-reset links.

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
None
Authentication
X
User interaction
A
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/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 installation and version
    Locate the NocoDB installation directory and check the package.json file for the version number, or run 'nc-db --version' or check the UI footer for the version display
    Affected if The installed version is prior to 2026.04.1
  2. Confirm password-reset page uses EJS templates
    Search the NocoDB source code for the password-reset template file (commonly in views or templates directory) and verify it contains EJS syntax with '<%= %>' tags embedding the reset token
    Affected if The password-reset template uses unescaped '<%= %>' tags for the token without additional JS escaping
  3. Verify the server-side rendering context
    Examine the password-reset route handler to confirm the token is passed directly to the EJS template without sanitization or JSON encoding
    Affected if The token parameter is passed to the template without escaping single quotes or backslashes for JavaScript context
  4. Check network response for token reflection
    Request the password-reset page with a test token containing special characters (single quote, backslash) and inspect the HTML source to see if characters are reflected as-is
    Affected if The token value appears in the page source without proper JavaScript string escaping (backslash for backslashes, \' for single quotes)

You are affected if NocoDB version is prior to 2026.04.1 AND the password-reset template uses EJS '<%= %>' tags that reflect the token without JavaScript-safe escaping.

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.04.1 or later. Until then, users should not click on untrusted password-reset links.

Recommended fix High confidence

2026.04.1 or later

  1. Backup your NocoDB installation and database before upgrading
  2. Upgrade NocoDB to version 2026.04.1 or later
  3. Verify the upgrade completed successfully
  4. Test the password reset functionality to confirm the vulnerability is patched

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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