> 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-role-controlled-by-a-parameter.md).

# Função do usuário controlada por um parâmetro

Notas sobre função do usuário controlada por um 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.

### Função do usuário controlada por parâmetro da requisição

Este laboratório tem um painel de administração acessível via **/admin**, que determina se um usuário é administrador com base em um cookie **facilmente falsificável**. / O objetivo é acessar o painel de administração e depois excluir o usuário **carlos**. / 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-371ffbed32b40fdbff0ae13c835ccbd0a5a17b44%2Fimage%20(262).png?alt=media" alt=""><figcaption></figcaption></figure>

Após alterar o endereço de e-mail, notamos que um cookie simplesmente indica **verdadeiro** ou **falso** a função de administrador.

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

Ao alterar seu valor para **verdadeiro**, o painel de administração se torna acessível.

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

<figure><img src="https://783634792-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-aaceb25318aa308211c6e746bb6ac6561b1361d4%2Fimage%20(265).png?alt=media" alt="" width="537"><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-role-controlled-by-a-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.
