Skip to main content
HighCodeOWASP A10:2021CWE-918

How to fix: fetch() URL built from user input

fetch(req.query.url) or fetch(`https://api.example.com/${userPath}`) lets attackers redirect the request to internal hosts (http://localhost, http://169.254.169.254) or arbitrary external services.

Why it matters

Server-side request forgery to internal services, cloud metadata endpoints, or other external systems.

The `code-ssrf-fetch-user-input` check verifies that the server does not expose the `ssrf-fetch-user-input` weakness in the code category. The detection runs against the response headers, body, or auxiliary probes (DNS, TLS, async fetch) as appropriate.

How to fix it

  1. 1Build URLs from server-side allowlists, not from raw user input.
  2. 2Resolve the host and reject private/loopback IP ranges before issuing the fetch.
  3. 3Use a forward proxy that enforces the destination allowlist.

Code examples

Allowlist permitted hosts for outbound fetch

TypeScript
const ALLOWED_HOSTS = new Set(["api.stripe.com", "api.sendgrid.com"]);

async function safeFetch(url: string, options?: RequestInit) {
  const { hostname, protocol } = new URL(url);
  if (protocol !== "https:") throw new Error("HTTPS only");
  if (!ALLOWED_HOSTS.has(hostname)) throw new Error("Host not allowed");
  return fetch(url, { ...options, signal: AbortSignal.timeout(5_000) });
}

References

Detected automatically by VulnRadar. The check id is code-ssrf-fetch-user-input, stable across every scan so you can filter or diff on it.

See every code check

Questions

How severe is fetch() URL built from user input?
VulnRadar rates this high severity in the code category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
Does VulnRadar check for this automatically?
Yes. It runs as part of every scan under the check id code-ssrf-fetch-user-input, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does fetch() URL built from user input map to?
It maps to CWE-918. In the OWASP Top 10 it falls under A10:2021.

Missing a check?

The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.

Propose a checkHow a check is built

Scan your own site for fetch() url built from user input

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

How to fix: fetch() URL built from user input | VulnRadar