Password requirements not enforced on Sign-Up Page — weak/non-compliant passwords are being saved

Open
#2,101 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
javascript
Domain
authentication, frontend

Research direction

Start at the Enatega Multivendor sign-up page and trace its password validation and account-creation flow. Reproduce with pass123, abc, and another policy-invalid password; done means weak passwords are rejected and a clear requirements error is shown before account creation.

Written by the indexing model from the issue text.

Description

Describe the bug
On the Enatega Multivendor sign-up page, passwords that do not meet the defined requirements are still accepted and the account is created. This allows weak or non-compliant passwords to be saved.

To Reproduce
Steps to reproduce the behavior:

Go to the Enatega Multivendor website sign-up page.
Fill in the required fields.
3.In the Password field, enter a password that does not meet the policy (e.g., pass123, abc, or any short/simple password).
Submit the form.
Notice the account is created / the form is saved without any password validation error.
Expected behavior
The system should reject passwords that do not meet the password policy (for example: minimum length, include uppercase, number, special character — whatever the site policy is) and show a clear error message explaining the requirements. Weak passwords must not be saved.

Desktop (please complete the following information):

OS: [e.g. Desktop]
Browser [e.g. chrome]
Version [e.g. 22]
Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]
Additional context
Add any other context about the problem here.

Labels: Enatega Website, Bug

Dominant language
JavaScript
Stars
0
Forks
0
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from raymondjames090/food-ordering-system-java-eclipse

All issues in raymondjames090/food-ordering-system-java-eclipse

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.