> 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/multistep-clickjacking.md).
# Multi-Step Clickjacking
Multi-Step Clickjacking notes for PortSwigger Web Security Academy labs, including exploitation workflow, payload testing, Burp Suite validation, and remediation context.
### Multistep Clickjacking
**Objective:** fool the user to click on the Delete account button and then confirm the confirmation dialog by clicking successively on two lures: **"Click me first"** then **"Click me next"**.
**Credentials provided to connect to the account (lab):** `wiener:peter`
* The page contains a **remove account** button followed by a confirmation box ("Are you sure?") — so you have to trigger two successive actions.
* The idea is to superimpose two clickable areas (div lures) over a `iframe` pointing to the `/my-account` page: the first target is the **Delete account** button, the second target is the confirmation button which then appears.
* We make the iframe semi-transparent (or low opacity) so that the user sees the lure but actually clicks on the elements of the targeted page.
```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/clickjacking/multistep-clickjacking.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)