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

# WordPress — техники

Техники перечисления WordPress, определения версии, поиска плагинов, WPScan и брутфорса.

## Перечисление сайта WordPress

### Перечислить пользователей:

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