> 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/wordpress-cms-exploitation/wordpress-techniques.md). # WordPress - Técnicas Enumeración de WordPress, detección de versión, descubrimiento de plugins, WPScan y técnicas de fuerza bruta. ## Enumeración de sitios WordPress ### Enumerar usuarios:

### WordPress indica si un usuario existe:

### Comprueba la versión de WordPress: ```bash whatweb https://website.com ``` ### Encuentra vulnerabilidades de la versión con searchsploit: ```bash searchsploit wordpress user enumeration ``` ### Buscar plugins utilizados, incluidas las versiones: ```bash wpscan --url https://website.com ``` ### Encuentra plugins ocultos en el código fuente del sitio: ```bash curl -s -X GET "https://website.com/" | grep -oP 'plugins//K[^/]+' | sort -u ``` ### Encuentra vulnerabilidades con una [WPScan](https://wpscan.com/profile) token: ```bash wpscan --url https://website.com -e vp --api-token="ms2cBwllBoXKaLvhVsrwTIaeL1GBbS44WLlkeu5UWQ4" ``` ### Fuerza bruta de usuarios válidos: ```bash wpscan --url https://website.com -e u ``` ### Fuerza bruta de la contraseña después de identificar un usuario válido: ```bash wpscan --url https://website.com -U USER -P /usr/share/wordlists/rockyou.txt ``` --- # 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/wordpress-cms-exploitation/wordpress-techniques.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.