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

CVE-2026-46547

MEDIUM · 6.1 CVSS v3.1 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 →
68/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, a reflected XSS vulnerability exists in the Page Leaving Warning page. The ncRedirectUrl and ncBackUrl query parameters are used in window.location.href and <a> tag bindings without validation, allowing javascript: URI injection. 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 versions prior to 2026.04.1 contain a reflected XSS vulnerability in the Page Leaving Warning functionality. The ncRedirectUrl and ncBackUrl query parameters are directly used in window.location.href JavaScript bindings and <a> tag href attributes without any input validation or sanitization, allowing attackers to inject malicious javascript: URIs.

MitigationUpgrade to NocoDB version 2026.04.1 or later. If immediate upgrade is not possible, implement input validation to reject URLs that do not begin with http://, https://, or a relative path protocol.

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
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Check NocoDB version
    Access the NocoDB instance and navigate to the version information, typically found in the UI footer, settings menu, or by querying the API endpoint that returns version metadata. Compare the installed version to the affected range (prior to 2026.04.1).
    Affected if The installed version is lower than 2026.04.1
  2. Identify if ncRedirectUrl or ncBackUrl parameters are processed
    Review application traffic or source code to determine if the ncRedirectUrl and ncBackUrl query parameters are accepted and processed by the application.
    Affected if The application accepts and uses ncRedirectUrl or ncBackUrl parameters without sanitization
  3. Verify Page Leaving Warning functionality is present
    Navigate through the application or examine the JavaScript bundles to confirm the Page Leaving Warning feature is implemented and actively uses the vulnerable parameters.
    Affected if The Page Leaving Warning feature is enabled and utilizes the ncRedirectUrl or ncBackUrl parameters
  4. Test for unsanitized reflection in response
    Submit a request with a javascript: URI in the ncRedirectUrl or ncBackUrl parameter (for example: ?ncRedirectUrl=javascript:alert(1)) and inspect the HTML response to see if the value appears unmodified in a window.location.href binding or <a> tag href attribute.
    Affected if The submitted javascript: URI appears unsanitized in the page response within JavaScript or HTML context

A user is affected if they are running NocoDB versions prior to 2026.04.1 and the application exposes the ncRedirectUrl or ncBackUrl parameters without proper sanitization.

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. If immediate upgrade is not possible, implement input validation to reject URLs that do not begin with http://, https://, or a relative path protocol.

Recommended fix High confidence

2026.04.1

  1. Identify the current NocoDB installation method (Docker, npm, or other)
  2. Stop the current NocoDB service
  3. Pull or download NocoDB version 2026.04.1
  4. Deploy the updated version 2026.04.1
  5. Restart the NocoDB service
  6. Verify the upgrade was successful by checking the version
  7. Test that the ncRedirectUrl and ncBackUrl parameters are properly sanitized and no longer accept javascript: URIs

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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