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

# WordPress

列挙、WPScan、プラグイン発見、xmlrpc.phpブルートフォース、認証済みRCE、脆弱なプラグイン、LFI、漏えい認証情報のためのWordPressペンテストノート。

ユーザー列挙、バージョン検出、プラグイン探索、xmlrpc.php のブルートフォース、テーマエディタの RCE、プラグインの LFI、漏洩した認証情報に関する WordPress 侵害メモ。

<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>手法</h4></td><td>WordPress の列挙、バージョン検出、プラグイン探索、WPScan、およびブルートフォース手法。</td><td><a href="/ja/cms/wordpress-cms-exploitation/wordpress-techniques.md">WordPress - 手法</a></td></tr><tr><td><h3><i class="fa-wordpress" style="color:$primary;">:wordpress:</i></h3></td><td><h4>認証済み RCE</h4></td><td>テーマエディタの悪用、404.php ペイロード注入、PHP リバースシェル実行、curl によるトリガー、シェル昇格手順に関する WordPress 認証済み RCE のメモ。</td><td><a href="/ja/cms/wordpress-cms-exploitation/wordpress-authenticated-rce.md">WordPress（認証済み）- RCE</a></td></tr><tr><td><h3><i class="fa-wordpress" style="color:$primary;">:wordpress:</i></h3></td><td><h4>手動ブルートフォース</h4></td><td>wp.getUsersBlogs の検証、XML ペイロードの作成、POST リクエストのテスト、Bash による自動化、パスワード発見に関する WordPress xmlrpc.php のブルートフォースメモ。</td><td><a href="/ja/cms/wordpress-cms-exploitation/manual-brute-force-xmlrpc.php.md">手動ブルートフォース（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>プラグインのパス検出、任意ファイルのダウンロード、wp-config.php の開示、データベース認証情報、phpMyAdmin へのアクセスに関する WordPress ebook-download プラグインの LFI メモ。</td><td><a href="/ja/cms/wordpress-cms-exploitation/wordpress-plugin-ebook-download-lfi.md">WordPressプラグイン - Ebook-Download（LFI）</a></td></tr><tr><td><h3><i class="fa-wordpress" style="color:$primary;">:wordpress:</i></h3></td><td><h4>BlockyCore.jar 漏洩</h4></td><td>BlockyCore.jar の展開と認証情報の発見を通じた WordPress プラグイン情報の漏洩。</td><td><a href="/ja/cms/wordpress-cms-exploitation/situation-information-leakage-blockycore.jar.md">シナリオ - 情報漏えい（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/ja/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.