> 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/wordpress-techniques.md).

# WordPress - 技巧

WordPress 枚举、版本检测、插件发现、WPScan 和暴力破解技巧。

## WordPress 站点枚举

### 枚举用户：

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-5a75e083bd69efc1b7a29a614505d3f66630be3f%2FPasted%20image%2020230811201425.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

### WordPress 会指示某个用户是否存在：

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-0a6081cfc44f337f0a5ace8ec52ffbad2e4ff6d6%2FPasted%20image%2020230811201620.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

### 检查 WordPress 版本：

```bash
whatweb https://website.com
```

### 使用 searchsploit 查找版本漏洞：

```bash
searchsploit wordpress user enumeration
```

### 搜索已使用的插件，包括版本：

```bash
wpscan --url https://website.com
```

### 在站点源代码中查找隐藏插件：

```bash
curl -s -X GET "https://website.com/" | grep -oP 'plugins//K[^/]+' | sort -u
```

### 使用一个 [WPScan](https://wpscan.com/profile) 令牌：

```bash
wpscan --url https://website.com -e vp --api-token="ms2cBwllBoXKaLvhVsrwTIaeL1GBbS44WLlkeu5UWQ4"
```

### 暴力破解有效用户：

```bash
wpscan --url https://website.com -e u
```

### 在识别出有效用户后暴力破解密码：

```bash
wpscan --url https://website.com -U USER -P /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/wordpress-techniques.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.
