GitHub Advisoryadvisory · npm

GHSA-h29g-q5c2-9h4f Parse Server email verification resend page leaks user existence

MEDIUM Published 2026-03-19 Modified 2026-03-30 Official page ↗
Aliases
CVE-2026-33323
Ecosystem
npm
Packages
parse-server
Severity
Moderate
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Weaknesses
CWE-204
Reviewed
2026-03-19

Affected packages

• npm parse-server: >= 9.0.0, < 9.6.0-alpha.40 → fixed in 9.6.0-alpha.40 • npm parse-server: < 8.6.51 → fixed in 8.6.51

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.

Related

Alias · CVE (1)

  • CVE-2026-33323 Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. vulnerability

Weakness · CWE (1)

  • CWE-204 Observable Response Discrepancy weakness

References