The registration form (Crea tu cuenta) exhibits multiple critical validation defects, allowing numeric characters in text-only fields (Nombre, Segundo nombre, Apellido), lacking realistic birth date validations, and failing to explicitly define or inform the user which fields are mandatory despite utilizing asterisksspan_0span_0.
Issue Description
During the account creation step, several form components fail to properly sanitize or validate user inputspan_1span_1:
Numeric Inputs in Alphabetic Fields: Fields designated strictly for names (e.g., Nombre, Segundo nombre, Apellido) accept numeric inputs (such as "123", "456", "789") without triggering client-side validation errorsspan_2span_2.
Unrealistic Birth Date Validation: The date of birth field accepts invalid or unrealistic dates (e.g., 12/12/1970 or future/improbable dates) without checking age reasonableness parametersspan_3span_3.
Missing Mandatory Field Legend/Instructions: While asterisks (*) are appended to field labels, there is no explicit legend or helper text explaining that asterisks denote mandatory fields, creating ambiguity for the userspan_4span_4.
Preconditions
The user is on the Crea tu cuenta (Personal Information / Account Creation) stepspan_5span_5.
Form input fields (Nombre, Segundo nombre, Apellido, Fecha de nacimiento) are active and editablespan_6span_6.
Steps to Reproduce
Navigate to the account creation page (Crea tu cuenta)span_7span_7.
In text-only fields such as Nombre, Segundo nombre, or Apellido, enter numbers instead of text (e.g., typing 123, 456, 789)span_8span_8.
Enter an unrealistic or arbitrary date in the Fecha de nacimiento field (e.g., 12/12/1970 or invalid ranges)span_9span_9.
Observe that the form accepts these inputs without showing validation blocks or explaining what the asterisks meanspan_10span_10.
Expected Result
Text-only fields (Nombre, Segundo nombre, Apellido) should strictly restrict input to alphabetic characters and standard name symbols, rejecting numbers.
The Fecha de nacimiento field should validate logical age constraints (e.g., reasonable age ranges, minimum/maximum limits).
The interface should provide an explicit helper text or legend (e.g., "* Campos obligatorios") to inform users what the asterisks signify.
Actual Result
The system allows numbers in name fields (123, 456, 789)span_11span_11.
Unrealistic dates (e.g., 12/12/1970) are accepted by the date picker/input without proper business logic validationspan_12span_12.
Asterisks are used on labels, but no disclaimer or instruction clarifies which fields are mandatory.
Date of Birth Field: Fecha de nacimiento* with input: 12/12/1970span_16span_16
UI Context: "Crea tu cuenta" form step showing lack of input sanitization and missing mandatory field guidancespan_17span_17.
Impact
Data Integrity: Corrupted or mock data (numbers in names, invalid dates) can easily be submitted to the database.
User Experience (UX): Poor guidance regarding mandatory fields and lack of input restrictions lead to user confusion and submission errors.
Frequency
Always
Reproducibility
100%
Notes & Recommendations
Implement strict regex patterns or input mask constraints on text fields to block numeric characters.
Add robust date-of-birth validation rules on both frontend and backend to enforce realistic age limits.
Include a clear form legend at the top or bottom of the section stating that fields marked with an asterisk (*) are mandatory.
## Summary
The registration form (Crea tu cuenta) exhibits multiple critical validation defects, allowing numeric characters in text-only fields (Nombre, Segundo nombre, Apellido), lacking realistic birth date validations, and failing to explicitly define or inform the user which fields are mandatory despite utilizing asterisks[span_0](start_span)[span_0](end_span).
## Issue Description
During the account creation step, several form components fail to properly sanitize or validate user input[span_1](start_span)[span_1](end_span):
1. *Numeric Inputs in Alphabetic Fields:* Fields designated strictly for names (e.g., Nombre, Segundo nombre, Apellido) accept numeric inputs (such as "123", "456", "789") without triggering client-side validation errors[span_2](start_span)[span_2](end_span).
2. *Unrealistic Birth Date Validation:* The date of birth field accepts invalid or unrealistic dates (e.g., 12/12/1970 or future/improbable dates) without checking age reasonableness parameters[span_3](start_span)[span_3](end_span).
3. *Missing Mandatory Field Legend/Instructions:* While asterisks (*) are appended to field labels, there is no explicit legend or helper text explaining that asterisks denote mandatory fields, creating ambiguity for the user[span_4](start_span)[span_4](end_span).
## Preconditions
- The user is on the *Crea tu cuenta* (Personal Information / Account Creation) step[span_5](start_span)[span_5](end_span).
- Form input fields (Nombre, Segundo nombre, Apellido, Fecha de nacimiento) are active and editable[span_6](start_span)[span_6](end_span).
## Steps to Reproduce
1. Navigate to the account creation page (Crea tu cuenta)[span_7](start_span)[span_7](end_span).
2. In text-only fields such as Nombre, Segundo nombre, or Apellido, enter numbers instead of text (e.g., typing 123, 456, 789)[span_8](start_span)[span_8](end_span).
3. Enter an unrealistic or arbitrary date in the Fecha de nacimiento field (e.g., 12/12/1970 or invalid ranges)[span_9](start_span)[span_9](end_span).
4. Observe that the form accepts these inputs without showing validation blocks or explaining what the asterisks mean[span_10](start_span)[span_10](end_span).
## Expected Result
- Text-only fields (Nombre, Segundo nombre, Apellido) should strictly restrict input to alphabetic characters and standard name symbols, rejecting numbers.
- The Fecha de nacimiento field should validate logical age constraints (e.g., reasonable age ranges, minimum/maximum limits).
- The interface should provide an explicit helper text or legend (e.g., "* Campos obligatorios") to inform users what the asterisks signify.
## Actual Result
- The system allows numbers in name fields (123, 456, 789)[span_11](start_span)[span_11](end_span).
- Unrealistic dates (e.g., 12/12/1970) are accepted by the date picker/input without proper business logic validation[span_12](start_span)[span_12](end_span).
- Asterisks are used on labels, but no disclaimer or instruction clarifies which fields are mandatory.
## Evidence
- *Personal Information Fields:*
- Nombre* with input: 123[span_13](start_span)[span_13](end_span)
- Segundo nombre* with input: 456[span_14](start_span)[span_14](end_span)
- Apellido* with input: 789[span_15](start_span)[span_15](end_span)
- *Date of Birth Field:* Fecha de nacimiento* with input: 12/12/1970[span_16](start_span)[span_16](end_span)
- *UI Context:* "Crea tu cuenta" form step showing lack of input sanitization and missing mandatory field guidance[span_17](start_span)[span_17](end_span).
## Impact
- *Data Integrity:* Corrupted or mock data (numbers in names, invalid dates) can easily be submitted to the database.
- *User Experience (UX):* Poor guidance regarding mandatory fields and lack of input restrictions lead to user confusion and submission errors.
## Frequency
Always
## Reproducibility
100%
## Notes & Recommendations
- Implement strict regex patterns or input mask constraints on text fields to block numeric characters.
- Add robust date-of-birth validation rules on both frontend and backend to enforce realistic age limits.
- Include a clear form legend at the top or bottom of the section stating that fields marked with an asterisk (*) are mandatory.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
The registration form (Crea tu cuenta) exhibits multiple critical validation defects, allowing numeric characters in text-only fields (Nombre, Segundo nombre, Apellido), lacking realistic birth date validations, and failing to explicitly define or inform the user which fields are mandatory despite utilizing asterisksspan_0span_0.
Issue Description
During the account creation step, several form components fail to properly sanitize or validate user inputspan_1span_1:
Preconditions
Steps to Reproduce
Expected Result
Actual Result
Evidence
Impact
Frequency
Always
Reproducibility
100%
Notes & Recommendations