> 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/clickjacking/basic-clickjacking-with-csrf-protection.md).
# Basic Clickjacking with CSRF Protection
Basic Clickjacking with CSRF Protection notes for PortSwigger Web Security Academy labs, including exploitation workflow, payload testing, Burp Suite validation, and remediation context.
### Basic Clickjacking with CSRF Token Protection
This lab contains a connection feature as well as a Delete account button protected by a **CRF token**. / The aim is to encourage the user to click on an item displaying the word "Click" on a lure site, so as to delete his account.
**Provided credentials:**
* wiener : peter
On the account page, we find the function **Delete account**.
The idea is to use a **`
```
This step allows us to display the target page in our own site.
Place misleading text ("Click") exactly above the *Delete account* button:
```html
Click
```
If the bottom of the page does not appear, it is probably due to the absence of the `frameborder="0"` parameter or to a site security policy. / The appearance can be adjusted as follows:
---
# 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/clickjacking/basic-clickjacking-with-csrf-protection.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.
.png?alt=media)
.png?alt=media)
.png?alt=media)