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

# Pluck

CVE-2023-50564の認証済みRCE、管理者ログインアクセス、ZIPペイロードアップロード、PHPリバースシェル、www-dataアクセスのためのPluck CMS攻略ノート。

## Pluckの脆弱性 /\[CVE-2023-50564] <a href="#pluck-content-manager-vulnerability" id="pluck-content-manager-vulnerability"></a>

ポート80でPluckのWebサービスが公開されています。

<figure><img src="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-5ca1aa9be90ef138bbef19d3bc1944e9d8b8bc55%2Fimage%20(1439).png?alt=media" alt=""><figcaption></figcaption></figure>

その `login.php` このファイルは、マネージャーインターフェースにアクセスするためにパスワードが必要です。

<figure><img src="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-f600d8f34593b8056f682ff09f8b79a5760cc7f3%2Fimage%20(1422).png?alt=media" alt=""><figcaption></figcaption></figure>

コンテンツマネージャーのバージョンは `4.7.18`、これはリモートコード実行（RCE）に対して脆弱です。

<figure><img src="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-8f3f8b3a1a533dc9212ad9832159f3935bd6e700%2Fimage%20(1423).png?alt=media" alt=""><figcaption></figcaption></figure>

{% embed url="<https://github.com/Rai2en/CVE-2023-50564_Pluck-v4.7.18_PoC>" %}

### 悪用フェーズ：

1. エクスプロイトスクリプトを含むリポジトリをクローンします：

```bash
git clone https://github.com/Rai2en/CVE-2023-50564_Pluck-v4.7.18_PoC.git
cd CVE-2023-50564_Pluck-v4.7.18_PoC
```

2. 変更する `poc.py` サーバーIPとパスワードを `_iloveyou1_`.

<figure><img src="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-c3f4b1ad4dbd97d1425706b31a828f6e8812d9be%2Fimage%20(2254).png?alt=media" alt=""><figcaption></figcaption></figure>

2. 次に作成します `payload.zip` を含む [`shell.php`](https://raw.githubusercontent.com/pentestmonkey/php-reverse-shell/refs/heads/master/php-reverse-shell.php)、次の項目を更新し、 `your_ip` およびリスナーポートの欄。

<figure><img src="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-5b26d0dadbe511e590433dc410a25dae2bd1f3f9%2Fimage%20(1429).png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

<figure><img src="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-bd9c3fb2f69f34eaef8d43f6f3d923d372439ea4%2Fimage%20(1430).png?alt=media" alt="" width="512"><figcaption></figcaption></figure>

5. エクスプロイトスクリプトを実行します：

```bash
python poc.py

/home/jordan/......./payload.zip
```

<figure><img src="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-2b35af275e12157310987ddbb1f90f7438833811%2Fimage%20(1420).png?alt=media" alt=""><figcaption></figcaption></figure>

同時に、ポート上でNetcatリスナーを開き `4444` 、次としてサーバーアクセスを取得します `www-data`.

<figure><img src="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-fe07098635cc4babcd46f24eb5983c47d9a04a89%2Fimage%20(1421).png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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/pluck-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.
