> 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/limesurvey-cms-exploitation.md). # LimeSurvey Notas de explotación de LimeSurvey 6.6.4 para RCE autenticada, creación de paquetes de plugins maliciosos, abuso de config.xml, reverse shell en PHP y orientación por ID de plugin. ## Vulnerabilidad en LimeSurvey CMS {% embed url="" %}

#### Acceso al área de administración La interfaz de administración está disponible en la siguiente URL: `http://take-survey.heal.htb/index.php/admin` Inicia sesión con las credenciales de Ralph: * **Nombre de usuario** : `ralph` * **Contraseña** : `147258369`

La versión de LimeSurvey es **6.6.4**, que es vulnerable a **Ejecución remota de código (RCE)**.

### Explotación de RCE a través de una extensión maliciosa {% embed url="" %} Adapta el script de explotación al contexto del objetivo.

Primero, crea un archivo comprimido que contenga `config.xml` y una shell inversa en PHP: ```bash zip -r N4s1rl1.zip config.xml revshell.php ```

Luego instala el complemento malicioso a través de la interfaz web de LimeSurvey.

Pasa el cursor sobre el complemento instalado para identificar el ID del complemento.

Después de actualizar el script con ese ID, inicia un listener en el puerto 443: ```bash nc -nlvp 443 ``` Finalmente, ejecuta el exploit con Python: ```bash python3 exploit.py http://take-survey.heal.htb ralph 147258369 80 ```

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