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).
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.
There is no known workaround.
{
"github_reviewed": true,
"github_reviewed_at": "2026-03-11T00:36:13Z",
"severity": "MODERATE",
"nvd_published_at": "2026-03-11T20:16:16Z",
"cwe_ids": [
"CWE-204"
]
}