Skip to main content
LowContentOWASP A05:2021CWE-200

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

  1. 1Review if phone numbers should be displayed.

Code examples

Mask phone numbers in API responses

TypeScript
// 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.

See every content check

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.

Propose a checkHow a check is built

Scan your own site for multiple phone numbers exposed

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: Multiple Phone Numbers Exposed | VulnRadar