> 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/wordpress-cms-exploitation/situation-information-leakage-blockycore.jar.md).
# Scénario - Fuite d’informations (BlockyCore.jar)
Fuite d’informations d’un plugin WordPress via l’extraction de BlockyCore.jar et la découverte d’identifiants.
**Énumération des répertoires avec Gobuster :**
Utilisez **Gobuster** pour énumérer les répertoires sur le serveur web cible.
```bash
gobuster dir -u http://blocky.htb/ -w /usr/share/SecLists/Discovery/Web-Content/directory-list-2.3-medium.txt -t 100
```
Un répertoire nommé **plugins** est découvert.
**Télécharger et extraire BlockyCore.jar :**
Télécharger **BlockyCore.jar**, qui semble être un plugin personnalisé, puis l'extraire.
```java
jar xf BlockyCore.jar
```
#### Décompilation de BlockyCore.class
Le contenu extrait comprend **BlockyCore.class**. Le décompiler avec **javap** pour inspecter le contenu.
```bash
javap -c BlockyCore.class
```
Un ensemble d'identifiants de base de données est trouvé :
* **localhost**
* **root**
* **8YsqfCTnvxAUeduzjNSXe22**
#### Accès à la base de données via phpMyAdmin
En utilisant les identifiants extraits, connectez-vous à **phpMyAdmin** et trouvez une table de base de données contenant l'utilisateur **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/fr/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)