GHSA-h29g-q5c2-9h4f

Parse Server email verification resend page leaks user existence

At a glance

Published
Updated
CVE
CVE-2026-33323
Aliases
BIT-parse-2026-33323
CVSS_V3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CVSS_V4
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Description

### Impact The Pages route and legacy PublicAPI route for resending email verification links return distinguishable responses depending on whether the provided username exists and has an unverified email. This allows an unauthenticated attacker to enumerate valid usernames by observing different redirect targets. The existing `emailVerifySuccessOnInvalidEmail` configuration option, which is enabled by default and protects the API route against this, did not apply to these routes. ### Patches The email verification resend routes now respect the `emailVerifySuccessOnInvalidEmail` option. When set to `true` (the default), both routes redirect to the success page regardless of the outcome, preventing user enumeration. ### Workarounds There is no known workaround to prevent the information disclosure other than upgrading.

Affected packages

PackageVersions
npm · parse-serverintroduced 9.0.0, fixed 9.6.0-alpha.40
npm · parse-serverintroduced 0, fixed 8.6.51

References

Sources

SourceLicence
OSV.devCC-BY 4.0 — GitHub Advisory Database