How to fix: axios.defaults.baseURL set to dev server
Hard-coded axios.defaults.baseURL = 'http://localhost:3000' will leak into production builds.
Why it matters
Move API base URLs to environment variables
Hard-coded axios.defaults.baseURL = 'http://localhost:3000' will leak into production builds.
How to fix it
- 1Move API base URLs to environment variables
Code examples
Set baseURL to a specific origin
import axios from "axios";
// BAD: base URL constructed from user input
// axios.defaults.baseURL = userInput + "/api";
// GOOD: hard-coded origin
const api = axios.create({
baseURL: process.env.NEXT_PUBLIC_API_URL || "https://api.yoursite.com",
timeout: 10_000,
withCredentials: false, // only enable if needed with explicit CORS
});References
Detected automatically by VulnRadar. The check id is code-axios-defaults-baseurl, 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 axios.defaults.baseURL set to dev server?
- VulnRadar rates this info 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-axios-defaults-baseurl, which stays the same between runs so you can filter, diff, or gate CI on it.
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.