> 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/csrf/csrf-token-validation-depends-on-http-method.md).
# CSRF con validación de token basada en el método HTTP
Notas de CSRF con validación de token basada en el método HTTP para laboratorios de PortSwigger Web Security Academy, incluido el flujo de explotación, pruebas de payloads, validación con Burp Suite y contexto de remediación.
### CSRF donde la validación del token depende del método de la solicitud
#### Contexto del laboratorio
La función de cambio de correo electrónico es vulnerable a un ataque CSRF. Hay una defensa, pero solo se aplica a ciertos tipos de solicitudes. Propósito: Alojar una página en el servidor de explotación que obligue a la víctima a cambiar su dirección de correo electrónico. / Credenciales proporcionadas para las pruebas: `wiener:peter`.
#### Constatación
* Se comprueba un token CSRF para **POST** solicitudes.
* La misma acción aceptada en **GET** \*\*n
* Punto en cuestión: `/my-account/change-email`.
El alojamiento en el servidor ejecuta una página que envía automáticamente una **GET** solicitud al endpoint de cambio de correo electrónico:
```html
```
La siguiente URL ilustra la omisión (no se requiere token en GET)
```html
/my-account/change-email?email=test%40test.com
```
---
# 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/csrf/csrf-token-validation-depends-on-http-method.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.
