> 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/situation-information-leakage-blockycore.jar.md).
# Escenario - Fuga de información (BlockyCore.jar)
Fuga de información de plugin de WordPress mediante extracción de BlockyCore.jar y descubrimiento de credenciales.
**Enumeración de directorios con Gobuster:**
Use **Gobuster** para enumerar directorios en el servidor web objetivo.
```bash
gobuster dir -u http://blocky.htb/ -w /usr/share/SecLists/Discovery/Web-Content/directory-list-2.3-medium.txt -t 100
```
Un directorio llamado **plugins** es descubierto.
**Descargar y extraer BlockyCore.jar:**
Descargar **BlockyCore.jar**, que parece ser un plugin personalizado, luego extráelo.
```java
jar xf BlockyCore.jar
```
#### Descompilando BlockyCore.class
El contenido extraído incluye **BlockyCore.class**. Descompílalo con **javap** para inspeccionar el contenido.
```bash
javap -c BlockyCore.class
```
Se encuentra un conjunto de credenciales de base de datos:
* **localhost**
* **root**
* **8YsqfCTnvxAUeduzjNSXe22**
#### Acceso a la base de datos a través de phpMyAdmin
Usando las credenciales extraídas, inicia sesión en **phpMyAdmin** y encuentra una tabla de la base de datos que contiene al usuario **notch**.
---
# 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/situation-information-leakage-blockycore.jar.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)