CVE-2026-63313 in 9router
Summary
by MITRE • 07/24/2026
9Router before 0.4.72 contains a server-side request forgery (SSRF) vulnerability in the /v1/web/fetch endpoint. The endpoint accepts a user-controlled url parameter and passes it to a configured external scraping provider (Firecrawl, Jina Reader, Tavily, or Exa) to fetch content. The URL is only validated as syntactically valid via new URL() with no blocklist for private IP ranges, cloud metadata endpoints (e.g., 169.254.169.254), link-local addresses, or internal hostnames. An authenticated or locally-connected user can cause the server to fetch arbitrary internal URLs and have the response content returned, enabling read-access SSRF that can expose cloud metadata credentials, reach internal services, and bypass authentication on localhost endpoints.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 07/24/2026
This vulnerability represents a critical server-side request forgery flaw in the 9Router application affecting versions prior to 0.4.72. The issue manifests within the /v1/web/fetch endpoint which processes user-provided URL parameters for content retrieval from external scraping services including Firecrawl, Jina Reader, Tavily, and Exa. The fundamental technical flaw lies in inadequate input validation that relies solely on syntactic URL parsing through the new URL() constructor without implementing proper network access restrictions or address range filtering.
The vulnerability operates by accepting user-controlled URLs and directly forwarding them to external scraping providers without sufficient sanitization measures. This design flaw permits attackers to specify internal network addresses including private IP ranges, cloud metadata endpoints such as 169.254.169.254, link-local addresses, and internal hostnames that would normally be restricted from external access. The lack of comprehensive blocklists for these sensitive address types creates a pathway for attackers to bypass normal network security controls and gain unauthorized access to internal resources.
From an operational perspective, this vulnerability enables authenticated or locally-connected users to perform read-access server-side request forgery attacks that can expose cloud metadata credentials stored at well-known internal endpoints. Attackers can leverage this capability to reach internal services that may not be exposed to external networks, potentially bypassing authentication mechanisms on localhost endpoints and accessing sensitive data or functionality that should remain protected within the internal network infrastructure.
The security implications align with CWE-918 Server-Side Request Forgery (SSRF) which specifically addresses vulnerabilities where applications fetch resources based on user-supplied input without proper validation. This flaw also maps to ATT&CK technique T1071.004 Application Layer Protocol: DNS where attackers can use SSRF to indirectly access internal DNS services and network resources that would otherwise be restricted. The vulnerability demonstrates a classic lack of defense in depth principles where network boundary controls are bypassed through application-level processing of user input, creating an attack vector that can be exploited from within the trusted network perimeter.
Mitigation strategies should implement comprehensive URL validation including explicit blocklists for private IP ranges, cloud metadata endpoints, and internal hostnames. The application must enforce strict network access controls that prevent outbound requests to sensitive internal addresses regardless of user input. Additionally, implementing proper rate limiting and monitoring for unusual request patterns can help detect potential exploitation attempts. The fix should also include validating that the requested URLs resolve to public internet addresses only, and consider implementing a whitelist approach for allowed domains or IP ranges rather than relying on blacklisting potentially dangerous addresses.