How to fix: User Enumeration via Email
Error message reveals email existence.
Why it matters
Attackers can verify which emails are registered.
Different messages for valid/invalid emails enable enumeration.
How to fix it
- 1Use generic messages like 'If this email exists...'
Code examples
Use consistent responses to prevent email enumeration
// BAD: "Email not found" vs "Wrong password" reveals valid emails
// GOOD: always return the same message regardless of whether email exists
export async function POST(req: Request) {
const { email, password } = await req.json();
const user = await db.users.findByEmail(email);
const valid = user && await bcrypt.compare(password, user.passwordHash);
// Same response either way:
if (!valid) {
return Response.json({ error: "Invalid email or password" }, { status: 401 });
}
// issue session
}References
Detected automatically by VulnRadar. The check id is email-enumeration, 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 User Enumeration via Email?
- VulnRadar rates this medium 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 email-enumeration, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does User Enumeration via Email map to?
- It maps to CWE-204. In the OWASP Top 10 it falls under A07: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.