Skip to content

Security: Enforce email verification on registration (Issue #717) - #1433

Open
sahare77 wants to merge 1 commit into
Canopus-Labs:mainfrom
sahare77:fix/717-email-verification-bypassed
Open

Security: Enforce email verification on registration (Issue #717)#1433
sahare77 wants to merge 1 commit into
Canopus-Labs:mainfrom
sahare77:fix/717-email-verification-bypassed

Conversation

@sahare77

@sahare77 sahare77 commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Summary of What Has Been Done

During user registration, the isEmailVerified field is being hardcoded to rue when saving the new user to the database. This completely bypasses the email verification requirement, allowing anyone to register with fake or unowned email addresses.

Changes Made

  • Modified �ackend/controllers/authController.js.
  • Removed isEmailVerified: true from the user creation payload, defaulting it to alse.
  • Added logic to generate emailVerificationToken and trigger the sendVerificationEmail utility upon successful registration.

Impact it Made

  • Secures the platform from bot registrations and spam accounts.
  • Ensures only verified email owners can access authenticated features and consume server resources.

Closes #717

@coderabbitai

coderabbitai Bot commented Aug 6, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@sahare77, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 6 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 8d88c7ff-422c-4961-b2a7-1155112d7563

📥 Commits

Reviewing files that changed from the base of the PR and between 8acb5b8 and 0e66171.

📒 Files selected for processing (1)
  • backend/controllers/authController.js

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Email verification permanently disabled: isEmailVerified hardcoded to true on registration

1 participant