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

[GH-ISSUE #2803] [BUG] It should return USER_NOT_FOUND instead of success when there's no such user #9356

New Issue
Closed
opened 2026-04-13 04:47:40 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-13 04:47:40 -05:00
Owner
Copy Link

Originally created by @dsonet on GitHub (May 27, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/2803

25b7f4f2d6/packages/better-auth/src/plugins/email-otp/index.ts (L133-L141)

In this case, it should return:

throw new APIError("BAD_REQUEST", {
  message: ERROR_CODES.USER_NOT_FOUND,
});
Originally created by @dsonet on GitHub (May 27, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/2803 https://github.com/better-auth/better-auth/blob/25b7f4f2d6aeaa5f83be5b3b9e86b665ec06da28/packages/better-auth/src/plugins/email-otp/index.ts#L133-L141 In this case, it should return: ```javascript throw new APIError("BAD_REQUEST", { message: ERROR_CODES.USER_NOT_FOUND, }); ```
GiteaMirror added the locked label 2026-04-13 04:47:40 -05:00
GiteaMirror commented 2026-04-13 04:47:42 -05:00
Author
Owner
Copy Link

@dsonet commented on GitHub (May 27, 2025):

PR is here: https://github.com/better-auth/better-auth/pull/2804

<!-- gh-comment-id:2913257929 --> @dsonet commented on GitHub (May 27, 2025): PR is here: https://github.com/better-auth/better-auth/pull/2804
GiteaMirror commented 2026-04-13 04:47:42 -05:00
Author
Owner
Copy Link

@Kinfe123 commented on GitHub (May 27, 2025):

This behavior is intentional and implemented for security reasons. Specifically, it is designed this way to mitigate potential risks of attack during the "Forgot Password" flow. This is a common security pattern to prevent user enumeration attacks.

<!-- gh-comment-id:2914355533 --> @Kinfe123 commented on GitHub (May 27, 2025): This behavior is intentional and implemented for security reasons. Specifically, it is designed this way to mitigate potential risks of attack during the "Forgot Password" flow. This is a common security pattern to prevent user enumeration attacks.
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 locked
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#9356
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?