How to fix: XMLHttpRequest URL from user input
xhr.open("GET", userInput) or fetch via XHR with a user-supplied URL allows attackers to drive requests to arbitrary hosts when called server-side (e.g. in Node + jsdom or in service workers).
Why it matters
Server-side XHR can reach internal services or leak response contents through error messages.
The `code-ssrf-xhr-user-input` check verifies that the server does not expose the `ssrf-xhr-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
- 1Restrict XHR destinations to an allowlist of trusted hosts.
- 2Resolve the URL host and reject private IP ranges.
- 3Use the Fetch API with redirect: 'manual' to prevent silent host hopping.
Code examples
Validate URL before XHR
function safeXhr(url) {
const parsed = new URL(url, location.origin);
if (parsed.origin !== location.origin) {
throw new Error("Cross-origin XHR blocked");
}
const xhr = new XMLHttpRequest();
xhr.open("GET", parsed.href, true);
xhr.timeout = 5000;
xhr.send();
}References
Detected automatically by VulnRadar. The check id is code-ssrf-xhr-user-input, stable across every scan so you can filter or diff on it.
More code checks
- CriticalForm Submits Data Over Insecure HTTP
- MediumPotential Prototype Pollution Sinks Detected
- HighPotential Command Injection Vectors
- HighJWT Decoded Without Signature Verification
- HighPotential Path Traversal Vulnerability
- HighInsecure Authentication Mechanisms Detected
- HighPotential Insecure Deserialization
- Mediumeval() Usage in Inline Scripts
Questions
- How severe is XMLHttpRequest URL from user input?
- VulnRadar rates this medium 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-xhr-user-input, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does XMLHttpRequest URL 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.