How to fix: Multiple Phone Numbers Exposed
Many phone numbers found in page source.
Why it matters
Privacy concern, potential data leak.
Bulk phone numbers may indicate data exposure.
How to fix it
- 1Review if phone numbers should be displayed.
Code examples
Mask phone numbers in API responses
// Mask phone numbers before sending to clients
function maskPhone(phone: string) {
return phone.replace(/\d(?=\d{4})/g, "*"); // ***-***-1234
}
// In API response:
return Response.json({
user: {
id: user.id,
phone: maskPhone(user.phone), // masked, not full number
},
});References
Detected automatically by VulnRadar. The check id is phone-number-leak, 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 Multiple Phone Numbers Exposed?
- 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 phone-number-leak, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Multiple Phone Numbers Exposed 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.