> 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/pt-br/web/access-control/user-id-controlled-by-parameter.md).

# ID do usuário controlado por parâmetro

Notas sobre ID do usuário controlado por parâmetro para os laboratórios do PortSwigger Web Security Academy, incluindo fluxo de exploração, teste de payload, validação no Burp Suite e contexto de remediação.

### ID de usuário controlado por parâmetro de requisição

Este laboratório apresenta um **escalada horizontal de privilégios** problema na página da conta de usuário. / Para resolver o laboratório, você precisa recuperar a **chave de API do usuário carlos** e enviá-la como solução. / Você pode se conectar com as seguintes credenciais: **wiener:peter**.

<figure><img src="https://783634792-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-a08bfe05fefdc3c3a8596f9131af959621d5f410%2Fimage%20(266).png?alt=media" alt=""><figcaption></figcaption></figure>

Em nosso próprio painel de usuário (o de wiener), observamos que o ID da conta é transmitido em um parâmetro de URL.

Ao alterar esse parâmetro e substituir nosso ID por carlos, por exemplo:

```bash
/my-account?id=carlos
```

A página então exibe as informações da conta de carlos, permitindo-nos recuperar sua \*\*chave de API\*\*.

<figure><img src="https://783634792-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-dc12988a68052766c57783b17d62e136521f1985%2Fimage%20(267).png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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/pt-br/web/access-control/user-id-controlled-by-parameter.md?ask=<question>&goal=<user_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.
