> 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/fr/cms/limesurvey-cms-exploitation.md). # LimeSurvey Notes d’exploitation de LimeSurvey 6.6.4 pour RCE authentifiée, création d’un paquet de plugin malveillant, abus de config.xml, reverse shell PHP et ciblage par ID de plugin. ## Vulnérabilité du CMS LimeSurvey {% embed url="" %}

#### Accès à la zone d’administration L’interface d’administration est disponible à l’URL suivante : `http://take-survey.heal.htb/index.php/admin` Connectez-vous avec les identifiants de Ralph : * **Nom d'utilisateur** : `ralph` * **Mot de passe** : `147258369`

La version de LimeSurvey est **6.6.4**, qui est vulnérable à **Exécution de code à distance (RCE)**.

### Exploitation du RCE via une extension malveillante {% embed url="" %} Adaptez le script d'exploitation au contexte de la cible.

Tout d’abord, créez une archive contenant `config.xml` et un shell inversé PHP : ```bash zip -r N4s1rl1.zip config.xml revshell.php ```

Installez ensuite le plugin malveillant via l’interface web de LimeSurvey.

Survolez le plugin installé pour identifier l’ID du plugin.

Après avoir mis à jour le script avec cet ID, lancez un écouteur sur le port 443 : ```bash nc -nlvp 443 ``` Enfin, exécutez l’exploit avec 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/fr/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.