parse-server
Affected
- introduced
9.0.0-alpha.1, fixed9.6.0-alpha.8(semver)
Fixed versions
9.6.0-alpha.8
Fix
- Fixed version
9.6.0-alpha.8npm install [email protected]
Advisory
Also known as: BIT-parse-2026-31901, CVE-2026-31901
Parse Server vulnerable to user enumeration via email verification endpoint
Impact
The email verification endpoint (/verificationEmailRequest) returns distinct error responses depending on whether an email address belongs to an existing user, is already verified, or does not exist. An attacker can send requests with different email addresses and observe the error codes to determine which email addresses are registered in the application.
This is a user enumeration vulnerability that affects any Parse Server deployment with email verification enabled (verifyUserEmails: true).
Patches
The fix introduces a new Parse Server option emailVerifySuccessOnInvalidEmail (default: true) that returns a generic success response for all verification email requests, regardless of whether the email address is valid, already verified, or non-existent. This prevents an attacker from distinguishing between these cases.
The fix also strengthens the input validation for the related resetPasswordSuccessOnInvalidEmail option, and adds security checks that warn when either enumeration mitigation is disabled.
Workarounds
There is no known workaround.
References
Medium Basis: The source's own band: MODERATE
9.0.0-alpha.1, fixed 9.6.0-alpha.8 (semver)9.6.0-alpha.8
9.6.0-alpha.8npm install [email protected]0, fixed 8.6.34 (semver)8.6.34
8.6.34npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0