How to fix: Hardcoded IP Addresses in Page Source
Multiple distinct IP addresses found hardcoded in page source (excluding localhost and common non-sensitive IPs).
Why it matters
Hardcoded IPs reveal server infrastructure and network topology.
IP addresses in client-facing code suggest hardcoded infrastructure references that should use DNS or environment variables.
How to fix it
- 1Replace hardcoded IPs with domain names.
- 2Use environment variables for server addresses.
- 3Configure DNS properly.
Code examples
Use DNS
const API = process.env.API_URL; // Not a hardcoded IPReferences
Detected automatically by VulnRadar. The check id is internal-ip-exposed, stable across every scan so you can filter or diff on it.
More content checks
- MediumPotential Open Redirect Parameters
- HighDirectory Listing Appears Enabled
- MediumSensitive File References Detected
- HighPotentially Outdated JavaScript Libraries
- Inforobots.txt Present - Review Manually
- InfoCMS / Technology Fingerprinting
- MediumPotentially Dangerous Inline JavaScript
- LowServer version disclosed in response header
Questions
- How severe is Hardcoded IP Addresses in Page Source?
- VulnRadar rates this low severity in the content 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 internal-ip-exposed, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Hardcoded IP Addresses in Page Source map to?
- It maps to CWE-200. In the OWASP Top 10 it falls under A05: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.