CVE-2026-33323: Parse Server email verification resend page leaks user existence
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.
Published Mar 19, 2026 · Updated Mar 30, 2026
Affected packages
parse-server
- Ecosystem
- npm
- Affected
- >= 9.0.0, < 9.6.0-alpha.40
- Fixed in
- 9.6.0-alpha.40
- Check
npm ls parse-server
parse-server
- Ecosystem
- npm
- Affected
- < 8.6.51
- Fixed in
- 8.6.51
- Check
npm ls parse-server
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
Credited to fancymalware, mtrezza.
References
- https://github.com/parse-community/parse-server/security/advisories/GHSA-h29g-q5c2-9h4f
- https://github.com/parse-community/parse-server/pull/10238
- https://github.com/parse-community/parse-server/pull/10243
- https://nvd.nist.gov/vuln/detail/CVE-2026-33323
- https://github.com/parse-community/parse-server/commit/967aa57732202009b2389ce9ecb3130d53d657e5
- https://github.com/parse-community/parse-server/commit/fbda4cb0c5cbc8fad08a216823b6b64d4ae289c3
- https://github.com/advisories/GHSA-h29g-q5c2-9h4f
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-61448
Parse Server vulnerable to stored XSS via malformed Content-Type bypassing file upload extension blocklist
low2.1Oct 29, 2026CVE-2026-50008
parse-server: Server option routeAllowList is bypassable through batch sub-requests
medium6.9Jun 19, 2026CVE-2026-53724
parse-server: Stored XSS via trailing-dot filename bypassing file upload extension blocklist
low2.1Jun 19, 2026CVE-2026-53725
parse-server: Endpoints `/login` and `/verifyPassword` disclose MFA secrets and protected fields when `_User` get is denied
medium5.9Jun 19, 2026CVE-2026-53726
parse-server: Relation `$relatedTo` query bypasses `protectedFields` and owning-object ACL
medium6.9Jun 19, 2026CVE-2026-55778
parse-server: Stored XSS via non-standard file extension bypassing file upload extension blocklist
low2.1Jun 19, 2026
