> 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/pt-br/cms/wordpress-cms-exploitation.md).

# WordPress

Notas de pentest de WordPress para enumeração, WPScan, descoberta de plugins, força bruta em xmlrpc.php, RCE autenticado, plugins vulneráveis, LFI e credenciais vazadas.

Notas de exploração do WordPress para enumeração de usuários, detecção de versão, descoberta de plugins, brute force em xmlrpc.php, RCE no editor de temas, LFI em plugin e credenciais vazadas.

<table data-view="cards" data-full-width="false" data-search="false"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h3><i class="fa-wordpress" style="color:$primary;">:wordpress:</i></h3></td><td><h4>Técnicas</h4></td><td>Enumeração do WordPress, detecção de versão, descoberta de plugins, WPScan e técnicas de brute force.</td><td><a href="/pt-br/cms/wordpress-cms-exploitation/wordpress-techniques.md">WordPress - Técnicas</a></td></tr><tr><td><h3><i class="fa-wordpress" style="color:$primary;">:wordpress:</i></h3></td><td><h4>RCE autenticado</h4></td><td>Notas de RCE autenticado no WordPress para abuso do editor de temas, injeção de payload em 404.php, execução de shell reverso em PHP, disparo com curl e etapas de atualização da shell.</td><td><a href="/pt-br/cms/wordpress-cms-exploitation/wordpress-authenticated-rce.md">WordPress (autenticado) - RCE</a></td></tr><tr><td><h3><i class="fa-wordpress" style="color:$primary;">:wordpress:</i></h3></td><td><h4>Brute Force Manual</h4></td><td>Notas de brute force em xmlrpc.php do WordPress para validação de wp.getUsersBlogs, criação de payload XML, testes de requisições POST, automação em Bash e descoberta de senhas.</td><td><a href="/pt-br/cms/wordpress-cms-exploitation/manual-brute-force-xmlrpc.php.md">Força Bruta Manual (xmlrpc.php)</a></td></tr><tr><td><h3><i class="fa-wordpress" style="color:$primary;">:wordpress:</i></h3></td><td><h4>LFI do Ebook-Download</h4></td><td>Notas de LFI do plugin ebook-download do WordPress para descoberta do caminho do plugin, download arbitrário de arquivos, divulgação do wp-config.php, credenciais do banco de dados e acesso ao phpMyAdmin.</td><td><a href="/pt-br/cms/wordpress-cms-exploitation/wordpress-plugin-ebook-download-lfi.md">Plugin do WordPress - Ebook-Download (LFI)</a></td></tr><tr><td><h3><i class="fa-wordpress" style="color:$primary;">:wordpress:</i></h3></td><td><h4>Vazamento do BlockyCore.jar</h4></td><td>Vazamento de informações de plugin do WordPress por meio da extração do BlockyCore.jar e descoberta de credenciais.</td><td><a href="/pt-br/cms/wordpress-cms-exploitation/situation-information-leakage-blockycore.jar.md">Cenário - Vazamento de Informações (BlockyCore.jar)</a></td></tr></tbody></table>


---

# 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/pt-br/cms/wordpress-cms-exploitation.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.