github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-23 07:18:56 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[PR #5014] [MERGED] fix: use consistent messaging on requestPasswordReset #13967

New Issue
Closed
opened 2026-04-13 09:14:35 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-13 09:14:35 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/5014
Author: @Eazash
Created: 10/1/2025
Status: ✅ Merged
Merged: 10/1/2025
Merged by: @himself65

Base: canary ← Head: fix/consistent-reset-password-message

📝 Commits (1)

  • e3f5de1 fix: use consistent messaging on requestPasswordReset

📊 Changes

1 file changed (+2 additions, -0 deletions)

View changed files

📝 packages/better-auth/src/api/routes/reset-password.ts (+2 -0)

📄 Description

Make the message returned from requestPasswordReset consistent between when the user is found or not. This helps avoid user enumeration via the difference in behaviour.

Summary by cubic

Return a consistent success message in requestPasswordReset to prevent user enumeration. The endpoint now always responds with: "If this email exists in our system, check your email for the reset link".

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/better-auth/better-auth/pull/5014 **Author:** [@Eazash](https://github.com/Eazash) **Created:** 10/1/2025 **Status:** ✅ Merged **Merged:** 10/1/2025 **Merged by:** [@himself65](https://github.com/himself65) **Base:** `canary` ← **Head:** `fix/consistent-reset-password-message` --- ### 📝 Commits (1) - [`e3f5de1`](https://github.com/better-auth/better-auth/commit/e3f5de17b39e8ea0b59f9316e79ce70a307fb08f) fix: use consistent messaging on `requestPasswordReset` ### 📊 Changes **1 file changed** (+2 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `packages/better-auth/src/api/routes/reset-password.ts` (+2 -0) </details> ### 📄 Description Make the message returned from `requestPasswordReset` consistent between when the user is found or not. This helps avoid user enumeration via the difference in behaviour. <!-- This is an auto-generated description by cubic. --> --- ## Summary by cubic Return a consistent success message in requestPasswordReset to prevent user enumeration. The endpoint now always responds with: "If this email exists in our system, check your email for the reset link". <!-- End of auto-generated description by cubic. --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-13 09:14:35 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#13967
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?