[BUG]: User emails are visible to any logged-in user

Abierto
#807 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@krish858 ya está trabajando en esto.

Desde el 20/11/2026.

  • #809 de @krish858 — abierto

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
57/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript

Línea de trabajo

Start by locating the handlers for GET /teams/available and GET /teams/:id, then check their response shapes and access checks. Reproduce the requests with an authenticated user who is not on the team. Done means unauthorized users cannot retrieve team member emails or private team details, while permitted team discovery still works.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug
Bug Description

GET /teams/available returns every team that still has an open slot, with info like , team id , joining code, users(in that team),emails(of the users in the teams).

GET /teams/:id also returns whole info to any authenticated user.

Steps to Reproduce

1 Go to http://localhost:5173/team-builder in the network tab you can see the request available which is a get req to /teams/available with all the info about the current teams or can do a get request in post man.

2 if you have team id, you can just make a get req on /teams/:id it will again give you all info on that team without being on the team.

Logs and Screenshots
image image
Environment Details

No response

Impact

Medium - Feature works but has issues

Code of Conduct
  • I have joined the Discord server and will post updates there
  • I have searched existing issues to avoid duplicates
Lenguaje dominante
TypeScript
Estrellas
108
Forks
264
Merge medio
6 h 53 min
PR fusionados (30 d)
8

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de AOSSIE-Org/DebateAI

Todos los issues de AOSSIE-Org/DebateAI

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.