Margaret-Petersen / Margaret-Petersen/python-based-food-ordering-system
Password requirements not enforced on Sign-Up Page — weak/non-compliant passwords are being saved
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the sign-up page entry point and trace how the password field is validated before the account is created. Identify the existing password policy, then verify that non-compliant passwords show a clear error and are not saved; add or update coverage where the sign-up flow is tested, if such a test exists.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- authentication, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100