> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/es/web/access-control/user-id-controlled-by-parameter.md).
# Id de usuario controlado por parámetro
Notas sobre Id de usuario controlado por parámetro para los laboratorios de PortSwigger Web Security Academy, incluido el flujo de explotación, pruebas de payload, validación en Burp Suite y contexto de mitigación.
### ID de usuario controlado por parámetro de solicitud
Este laboratorio presenta un **escalada horizontal de privilegios** problema en la página de la cuenta de usuario. / Para resolver el laboratorio, necesitas recuperar la **clave API del usuario carlos** y enviarla como solución. / Puedes conectarte con las siguientes credenciales: **wiener:peter**.
En nuestro propio panel de usuario (el de wiener), observamos que el ID de la cuenta se transmite en un parámetro de la URL.
Cambiando este parámetro y sustituyendo nuestro ID por carlos, por ejemplo:
```bash
/my-account?id=carlos
```
La página entonces muestra la información de la cuenta de carlos, lo que nos permite recuperar su \*\*clave API\*\*.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://hacking-notes.jord4n.pro/es/web/access-control/user-id-controlled-by-parameter.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
.png?alt=media)
.png?alt=media)