CVE-2026-24768: NocoDB has Unvalidated Redirect in Login Flow via continueAfterSignIn Parameter
Summary An unvalidated redirect (open redirect) vulnerability exists in NocoDB’s login flow due to missing validation of the continueAfterSignIn parameter. During authentication, NocoDB processes a user-controlled redirect value and conditionally performs client-side navigation without enforcing any restrictions on the destination’s origin, domain or protocol.
Published Jan 28, 2026
Affected packages
nocodb
- Ecosystem
- npm
- Affected
- < 0.301.0
- Fixed in
- 0.301.0
- Check
npm ls nocodb
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
An unvalidated redirect (open redirect) vulnerability exists in NocoDB’s login flow due to missing validation of the continueAfterSignIn parameter.
During authentication, NocoDB processes a user-controlled redirect value and conditionally performs client-side navigation without enforcing any restrictions on the destination’s origin, domain or protocol. This allows attackers to redirect authenticated users to arbitrary external websites after login.
Root Cause
The redirect logic relies on a permissive URL check that treats any absolute or protocol-relative URL as safe, and performs navigation without applying an allowlist or origin validation.
In the redirect plugin:
- The helper function
isFullUrluses the following regular expression:
/^(https?:)?\/\//This pattern matches any HTTP(S) URL as well as protocol-relative URLs (e.g., //evil.example), without restricting allowed domains.
- When the
continueAfterSignInquery parameter matches this pattern, the application performs an unconditional external navigation:
navigateTo(route.value.query.continueAfterSignIn as string, {
external: isFullUrl(...)
})Attack Scenario
An attacker can exploit this issue through a phishing attack:
- The attacker crafts a malicious login URL containing a controlled redirect target, for example:
https://victim-nocodb.example/#/signin?continueAfterSignIn=https://evil-phishing.com/fake-login- The victim clicks the link and is presented with the legitimate NocoDB login page.
- The victim authenticates using valid credentials.
- After login, NocoDB automatically redirects the victim to the attacker-controlled external site.
- The attacker’s site displays a fake error message and prompts the victim to re-enter credentials.
- The victim unknowingly submits credentials to the attacker.
Impact
This vulnerability enables phishing attacks by leveraging user trust in the legitimate NocoDB login flow. While it does not directly expose credentials or bypass authentication, it increases the likelihood of credential theft through social engineering.
The issue does not allow arbitrary code execution or privilege escalation, but it undermines authentication integrity.
Credit
This issue was discovered by an AI agent developed by the GitHub Security Lab and reviewed by GHSL team members @p- (Peter Stöckli) and @m-y-mo (Man Yue Mo).
Credited to p-.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-53927
NocoDB: Server-Side Request Forgery via Spreadsheet Fetch URL
medium5.1No fixJun 17, 2026CVE-2026-53928
NocoDB: Refresh Tokens Persist Through Password Recovery
medium6.3No fixJun 17, 2026CVE-2026-53929
NocoDB: Stored Cross-Site Scripting via Secure Attachment
medium5.1No fixJun 17, 2026CVE-2026-53930
NocoDB: Server-Side Request Forgery via Base Migration URL
medium5.1No fixJun 17, 2026CVE-2026-53931
NocoDB: Server-Side Request Forgery via Spreadsheet Import Endpoint
medium6.9No fixJun 17, 2026CVE-2026-47279
NocoDB: Hidden LTAR Column Exposure in Public Shared-View Relation Endpoints
medium6.9Jun 5, 2026
