Skip to main content
HighCodeOWASP A10:2021CWE-918

How to fix: axios.get with user-controlled URL

axios.get(req.body.url) or axios({ url: `https://api/${userId}` }) issues HTTP from the server with attacker-controlled destinations, enabling SSRF and credential theft from metadata endpoints.

Why it matters

Outbound requests reach internal services or cloud metadata APIs that the attacker cannot otherwise reach.

The `code-ssrf-axios-user-input` check verifies that the server does not expose the `ssrf-axios-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. 1Validate the URL against an allowlist of permitted hosts and paths.
  2. 2Resolve the host and block private IP ranges (RFC 1918, loopback, link-local).
  3. 3Disable axios follow-redirects or re-validate after each redirect.

Code examples

Validate URL before axios request

TypeScript
import axios from "axios";

const ALLOWED = new Set(["api.example.com"]);

export async function proxyRequest(url: string) {
  const parsed = new URL(url);
  if (!ALLOWED.has(parsed.hostname)) throw new Error("Host blocked");
  if (parsed.protocol !== "https:") throw new Error("HTTPS only");
  return axios.get(parsed.href, { timeout: 5_000 });
}

References

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

See every code check

Questions

How severe is axios.get with user-controlled URL?
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-axios-user-input, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does axios.get with user-controlled URL 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 axios.get with user-controlled url

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: axios.get with user-controlled URL | VulnRadar