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

# WordPress

WordPress-Pentesting-Notizen für Enumeration, WPScan, Plugin-Entdeckung, xmlrpc.php-Brute-Force, authentifizierte RCE, verwundbare Plugins, LFI und geleakte Credentials.

WordPress-Exploitation-Notizen für Benutzerzählung, Versionsbestimmung, Plugin-Erkennung, xmlrpc.php-Bruteforce, Theme-Editor-RCE, Plugin-LFI und geleakte Anmeldedaten.

<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>Techniken</h4></td><td>WordPress-Benutzerzählung, Versionsbestimmung, Plugin-Erkennung, WPScan und Brute-Force-Techniken.</td><td><a href="/de/cms/wordpress-cms-exploitation/wordpress-techniques.md">WordPress - Techniken</a></td></tr><tr><td><h3><i class="fa-wordpress" style="color:$primary;">:wordpress:</i></h3></td><td><h4>Authentifizierte RCE</h4></td><td>WordPress-Notizen zur authentifizierten RCE für Theme-Editor-Missbrauch, 404.php-Payload-Injektion, Ausführung einer PHP-Reverse-Shell, Triggern per curl und Schritte zum Upgrade der Shell.</td><td><a href="/de/cms/wordpress-cms-exploitation/wordpress-authenticated-rce.md">WordPress (authentifiziert) - RCE</a></td></tr><tr><td><h3><i class="fa-wordpress" style="color:$primary;">:wordpress:</i></h3></td><td><h4>Manueller Brute-Force-Angriff</h4></td><td>WordPress-xmlrpc.php-Bruteforce-Notizen für die Validierung von wp.getUsersBlogs, das Erstellen von XML-Payloads, das Testen von POST-Anfragen, Bash-Automatisierung und Passwortfindung.</td><td><a href="/de/cms/wordpress-cms-exploitation/manual-brute-force-xmlrpc.php.md">Manueller Brute Force (xmlrpc.php)</a></td></tr><tr><td><h3><i class="fa-wordpress" style="color:$primary;">:wordpress:</i></h3></td><td><h4>Ebook-Download-LFI</h4></td><td>WordPress-ebook-download-Plugin-LFI-Notizen für die Erkennung des Plugin-Pfads, beliebigen Dateidownload, Offenlegung von wp-config.php, Datenbankanmeldedaten und phpMyAdmin-Zugriff.</td><td><a href="/de/cms/wordpress-cms-exploitation/wordpress-plugin-ebook-download-lfi.md">WordPress-Plugin - Ebook-Download (LFI)</a></td></tr><tr><td><h3><i class="fa-wordpress" style="color:$primary;">:wordpress:</i></h3></td><td><h4>BlockyCore.jar-Leak</h4></td><td>WordPress-Plugin-Informationsleck durch Extraktion von BlockyCore.jar und Ermittlung von Anmeldedaten.</td><td><a href="/de/cms/wordpress-cms-exploitation/situation-information-leakage-blockycore.jar.md">Szenario - Informationsleck (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/de/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.