> 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/cms/wordpress-cms-exploitation.md). # WordPress WordPress pentesting notes for enumeration, WPScan, plugin discovery, xmlrpc.php brute force, authenticated RCE, vulnerable plugins, LFI, and leaked credentials. WordPress exploitation notes for user enumeration, version detection, plugin discovery, xmlrpc.php brute force, theme editor RCE, plugin LFI, and leaked credentials.

:wordpress:

Techniques

WordPress enumeration, version detection, plugin discovery, WPScan, and brute force techniques.WordPress - Techniques

:wordpress:

Authenticated RCE

WordPress authenticated RCE notes for theme editor abuse, 404.php payload injection, PHP reverse shell execution, curl triggering, and shell upgrade steps.WordPress (authenticated) - RCE

:wordpress:

Manual Brute Force

WordPress xmlrpc.php brute force notes for wp.getUsersBlogs validation, XML payload crafting, POST request testing, Bash automation, and password discovery.Manual Brute Force (xmlrpc.php)

:wordpress:

Ebook-Download LFI

WordPress ebook-download plugin LFI notes for plugin path discovery, arbitrary file download, wp-config.php disclosure, database credentials, and phpMyAdmin access.WordPress Plugin - Ebook-Download (LFI)

:wordpress:

BlockyCore.jar Leak

WordPress plugin information leakage through BlockyCore.jar extraction and credential discovery.Scenario - Information Leakage (BlockyCore.jar)
--- # 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/cms/wordpress-cms-exploitation.md?ask=&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.