NocoDB: Reflected Cross-Site Scripting via Page Leaving Redirect URL

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

EPSS

• CVE-2026-46547: 0.27% estimated exploitation activity in the next 30 days; percentile 18.46 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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. Details PageLeavingWarning.vue reads ncRedirectUrl and ncBackUrl directly from the route query without validation. When isSameOriginUrl() returns false (as it does for javascript: URIs), the raw URL is assigned to window.location.href, executing arbitrary JavaScript. The redirect URL is also bound directly to an <a tag's href attribute. Impact An attacker can execute arbitrary JavaScript in the context of the NocoDB application by sending a crafted link to a victim. No authentication is required. Credit This issue was reported by @naoyashiga.

Published by the source

21 May 2026, 20:34 UTC

Last modified by the source

20 Jul 2026, 21:30 UTC

Source last checked

26 Oct 2026, 12:57 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-9qgr-6vpg-9gh9

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-9qgr-6vpg-9gh9

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-46547

Advisory: NocoDB: Reflected Cross-Site Scripting via Page Leaving Redirect URL
IDs: CVE-2026-46547, GHSA-9qgr-6vpg-9gh9
Record: https://patchnext.com/advisories/cve-2026-46547 (revision 2, source checked 26 Oct 2026, 12:57 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm nocodb: affected <= 0.301.3

## Suggested inspection (read-only)
- `npm ls nocodb --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on nocodb.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-9qgr-6vpg-9gh9 (OSV record GHSA-9qgr-6vpg-9gh9 lists affected ranges: npm nocodb >=0 <=0.301.3)
- Verified: https://github.com/advisories/GHSA-9qgr-6vpg-9gh9 (GitHub-reviewed advisory GHSA-9qgr-6vpg-9gh9 lists affected ranges: npm nocodb >=0 <=0.301.3)

Commands are suggestions: review each one before running it.