GHSA-3hmw-8mw3-rmpj
NocoDB has Unvalidated Redirect in Login Flow via continueAfterSignIn Parameter
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
nocodbnpmDescription
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).
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | nocodb | all versions | 0.301.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nocodb. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update nocodb to 0.301.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3hmw-8mw3-rmpj is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-3hmw-8mw3-rmpj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-3hmw-8mw3-rmpj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-3hmw-8mw3-rmpj in your dependencies?
O3 detects GHSA-3hmw-8mw3-rmpj across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.