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

CVE-2026-47387

HIGH · 8.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 →
88/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, the shared form-view submit handler (packages/nc-gui/composables/useSharedFormViewStore.ts) in NocoDB writes the form's redirect_url to window.location.href after a same-host check that does not validate the URL scheme. A user with editor role (or above) on any base can plant a javascript: URL in the form's redirect_url; when an authenticated viewer opens the share-link and submits the form, the payload executes in the NocoDB origin and can read the session token from localStorage["nocodb-gui-v2"]. 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

Stored XSS vulnerability in NocoDB's shared form-view submit handler where the redirect_url parameter is not validated for URL scheme before being set to window.location.href. An attacker with editor role or above can plant a javascript: URL that executes in the context of authenticated viewers who submit the form, allowing theft of session tokens from localStorage.

MitigationUpgrade to NocoDB version 2026.05.1 or later, which implements proper URL scheme validation in the redirect_url handling logic.

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
A
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/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 installation and version
    Locate the NocoDB instance and check its version (typically visible in the UI footer, /api/v1/version endpoint, or Docker image tag). Compare against the fixed version 2026.05.1.
    Affected if Running any version of NocoDB prior to 2026.05.1.
  2. Confirm shared form-view feature is enabled
    Check if the NocoDB instance has shared views functionality enabled. This is typically found in project settings or workspace configuration.
    Affected if Shared form-views are enabled and accessible to users.
  3. Identify existing shared form views
    Enumerate all shared form views in the NocoDB instance. Look for entries in the UI under 'Share' for form views, or query the _shared_views or similar metadata tables if database access is available.
    Affected if There are shared form views configured in the environment.
  4. Inspect redirect_url settings in form views
    Examine the configuration of each shared form view for any redirect_url parameter. In the UI, check the form view settings or share URL configuration. If database access is available, query the view metadata for redirect_url values.
    Affected if Any shared form view has a redirect_url configured that uses an unexpected or javascript: scheme.
  5. Check user roles and permissions
    Review user accounts to identify users with editor role or above who could potentially create or modify shared form views.
    Affected if There are users with editor role or higher who have access to create or modify shared form views.

The environment is affected if running NocoDB versions before 2026.05.1 with shared form-view functionality enabled and users possessing editor role or above who can configure form view redirect URLs.

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 proper URL scheme validation in the redirect_url handling logic.

Recommended fix High confidence

2026.05.1

  1. 1. Back up your current NocoDB instance and database before proceeding with the upgrade.
  2. 2. Check your current NocoDB version to confirm it is prior to 2026.05.1.
  3. 3. Upgrade NocoDB to version 2026.05.1 or later following your deployment method (Docker, npm, or other).
  4. 4. After upgrade, verify the installation by checking the NocoDB version.
  5. 5. Confirm the vulnerability is patched by testing that javascript: URLs are no longer accepted in the redirect_url field of shared form-views.

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

Have this fixed 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 help mitigating

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-47387 — 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-47387 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