> 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/web/graphql/csrf-exploitation-via-graphql.md).
# CSRF Exploitation via GraphQL
CSRF Exploitation via GraphQL notes for PortSwigger Web Security Academy labs, including exploitation workflow, payload testing, Burp Suite validation, and remediation context.
### Performing CSRF Exploits Over GraphQL
#### Lab Context
User management features are based on a **GraphQL** endpoint. / Key point: l
**Objective:** Create an HTML page (hosted on the exploit server) that, when loaded by the victim, **changes its email address**.
#### GraphQL Query Observed
When you change the email from the application, the request sent looks like
```json
{
"query": "/n mutation changeEmail($input: ChangeEmailInput!) {/n changeEmail(input: $input) {/n email/n }/n }/n",
"operationName": "changeEmail",
"variables": {
"input": {
"email": "test@test.com"
}
}
}
```
### Method 1: Simple CSRF with Form (recommended)
The idea is to reproduce the GraphQL mutation via a **form POST** to the GraphQL endpoint, with `query`, `operationName` and `variables` fields.
Example of an operation to be deposited on the operator:
```javascript
```
Expected result: when the victim opens the page, his/her browser sends the request and **the email is changed**.
### Method 2: X-www-form-urlencoded
Here, you encode the parameters directly as would a classic form:
```bash
Content-Type: application/x-www-form-urlencoded
```
{% code overflow="wrap" %}
```bash
query=%0A++++mutation+changeEmail($input:+ChangeEmailInput!)+{%0A++++++++changeEmail(input:$input)+{%0A++++++++++++email%0A++++++++}%0A++++}%0A&operationName=changeEmail&variables={"input":{"email":"test@test.com"}}
```
{% endcode %}
Practical to quickly check what the request looks like.
From Burp:
1. Right click on the GraphQL request
2. **Commitment tools** → **Generate CSRF PoC**
3. Burp produces a ready-to-host HTML, for example:
```html
```
---
# 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/web/graphql/csrf-exploitation-via-graphql.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.
