dbcve.org
Open RedirectWeakness · CWE-601

CVE-2026-47377

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 8 weeks old

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 client-side hashRedirect plugin called window.location.replace() on a path extracted from the URL hash fragment after only checking hashPath.startsWith('/'). Protocol-relative URLs (//attacker.com/…) also satisfy that check, so a crafted link silently redirected visitors to an attacker-controlled origin. 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

This is a client-side open redirect vulnerability in NocoDB's hashRedirect plugin. The plugin extracts a path from the URL hash fragment and uses window.location.replace() for redirection after only checking if hashPath.startsWith('/'). Since protocol-relative URLs like //attacker.com/... also satisfy this check, attackers can craft malicious links that silently redirect users to attacker-controlled domains.

MitigationUpgrade NocoDB to version 2026.04.1 or later, which implements proper validation to reject protocol-relative URLs in the hashRedirect plugin.

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:N/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. Confirm NocoDB is present in your environment
    Check if NocoDB is installed by looking for its installation directory, running processes, or checking for the web application accessible on expected ports (default 8080). Query your container registry or deployment manifests if applicable.
    Affected if NocoDB is not found in your environment (not affected)
  2. Determine the installed NocoDB version
    Check the version of your NocoDB installation. This is typically visible in the application UI footer, in the package.json file if self-hosted, or by querying the /api/v1/version endpoint if the API is accessible.
    Affected if The installed version is earlier than 2026.04.1 (potentially affected)
  3. Verify the hashRedirect plugin is active
    Examine the NocoDB frontend JavaScript files or plugin configuration to determine if the hashRedirect plugin is enabled. Look for references to 'hashRedirect' in the codebase or plugin settings.
    Affected if The hashRedirect plugin is enabled and the version is before 2026.04.1 (affected)
  4. Inspect the vulnerable redirection code
    If you have access to the frontend source, locate the hashRedirect plugin JavaScript and examine the redirection logic. Check for code that uses window.location.replace() with a path derived from the URL hash and only validates with startsWith('/') without rejecting protocol-relative URLs starting with '//'.
    Affected if The code shows the vulnerable pattern of checking only startsWith('/') before using window.location.replace() with hash-derived input (confirmed affected)

You are affected if NocoDB with a version before 2026.04.1 has the hashRedirect plugin enabled and contains the vulnerable code pattern that only validates the hash path starts with '/' without blocking protocol-relative 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 NocoDB to version 2026.04.1 or later, which implements proper validation to reject protocol-relative URLs in the hashRedirect plugin.

Recommended fix Moderate confidence

2026.04.1

  1. Identify the currently deployed NocoDB version
  2. Locate the NocoDB installation method (Docker, npm, binary, or other)
  3. Pull or download NocoDB version 2026.04.1
  4. Deploy the updated version according to the installation method used
  5. Verify the deployment is successful and the application is running

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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