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

# WordPress

Notas de pentesting de WordPress para enumeración, WPScan, descubrimiento de plugins, fuerza bruta en xmlrpc.php, RCE autenticado, plugins vulnerables, LFI y credenciales filtradas.

Notas de explotación de WordPress para enumeración de usuarios, detección de versiones, descubrimiento de plugins, fuerza bruta en xmlrpc.php, RCE en el editor de temas, LFI en plugins y credenciales filtradas.

<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>Enumeración de WordPress, detección de versiones, descubrimiento de plugins, WPScan y técnicas de fuerza bruta.</td><td><a href="/es/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 en WordPress para el abuso del editor de temas, inyección de payload en 404.php, ejecución de una shell inversa de PHP, activación mediante curl y pasos para mejorar la shell.</td><td><a href="/es/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>Fuerza bruta manual</h4></td><td>Notas de fuerza bruta en xmlrpc.php de WordPress para validación de wp.getUsersBlogs, creación de payloads XML, pruebas de solicitudes POST, automatización en Bash y descubrimiento de contraseñas.</td><td><a href="/es/cms/wordpress-cms-exploitation/manual-brute-force-xmlrpc.php.md">Fuerza bruta manual (xmlrpc.php)</a></td></tr><tr><td><h3><i class="fa-wordpress" style="color:$primary;">:wordpress:</i></h3></td><td><h4>LFI de Ebook-Download</h4></td><td>Notas de LFI del plugin ebook-download de WordPress para descubrimiento de la ruta del plugin, descarga arbitraria de archivos, divulgación de wp-config.php, credenciales de la base de datos y acceso a phpMyAdmin.</td><td><a href="/es/cms/wordpress-cms-exploitation/wordpress-plugin-ebook-download-lfi.md">Plugin de WordPress - Ebook-Download (LFI)</a></td></tr><tr><td><h3><i class="fa-wordpress" style="color:$primary;">:wordpress:</i></h3></td><td><h4>Filtración de BlockyCore.jar</h4></td><td>Filtración de información del plugin de WordPress mediante la extracción de BlockyCore.jar y el descubrimiento de credenciales.</td><td><a href="/es/cms/wordpress-cms-exploitation/situation-information-leakage-blockycore.jar.md">Escenario - Fuga de información (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/es/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.