> 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/de/cms/wordpress-cms-exploitation/situation-information-leakage-blockycore.jar.md).
# Szenario - Informationsleck (BlockyCore.jar)
WordPress-Plugin-Informationsleck durch Extraktion von BlockyCore.jar und Credential-Entdeckung.
**Verzeichnis-Enumeration mit Gobuster:**
Verwenden Sie **Gobuster** um Verzeichnisse auf dem Ziel-Webserver aufzulisten.
```bash
gobuster dir -u http://blocky.htb/ -w /usr/share/SecLists/Discovery/Web-Content/directory-list-2.3-medium.txt -t 100
```
Ein Verzeichnis namens **plugins** wird entdeckt.
**BlockyCore.jar herunterladen und entpacken:**
Herunterladen **BlockyCore.jar**, das offenbar ein benutzerdefiniertes Plugin ist, und es dann extrahieren.
```java
jar xf BlockyCore.jar
```
#### BlockyCore.class dekompilieren
Der extrahierte Inhalt enthält **BlockyCore.class**. Dekompiliere es mit **javap** um den Inhalt zu prüfen.
```bash
javap -c BlockyCore.class
```
Es wird ein Satz von Datenbank-Anmeldedaten gefunden:
* **localhost**
* **root**
* **8YsqfCTnvxAUeduzjNSXe22**
#### Datenbankzugriff über phpMyAdmin
Melde dich mit den extrahierten Anmeldedaten bei **phpMyAdmin** an und finde eine Datenbanktabelle, die den Benutzer enthält **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/de/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)