# CVE-2018-9276: Paessler PRTG Network Monitor OS Command Injection

> Administrators can execute arbitrary OS commands via malformed parameters in sensor or notification management, requiring admin access.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 4 Feb 2025 (CISA KEV)
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jul 2018
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-cjqq-8xv6-575p

## What is CVE-2018-9276?

CVE-2018-9276 is a high-severity command injection vulnerability in n/a, published on 2 Jul 2018. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An issue was discovered in PRTG Network Monitor before 18.2.39. An attacker who has access to the PRTG System Administrator web console with administrative privileges can exploit an OS command injection vulnerability (both on the server and on devices) by sending malformed parameters in sensor or notification management scenarios.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2018-9276?

It affects 1 product.


Products: Paessler Prtg Network Monitor.

## How do I fix CVE-2018-9276?

No fix has been published for CVE-2018-9276 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 25 Feb 2025.

## Is CVE-2018-9276 being exploited?

Yes. Attackers have exploited CVE-2018-9276 in the wild since at least 4 Feb 2025.

Public exploit code:

- CVE-2018-9276 PRTG < 18.2.39 Authenticated Command Injection (Reverse Shell) (github_poc): https://github.com/wildkindcc/CVE-2018-9276
- PRTG Network Monitor Authenticated RCE (metasploit)
- PRTG Network Monitor 18.2.38 - (Authenticated) Remote Code Execution (exploitdb)
- https://github.com/andyfeili/CVE-2018-9276 (github_poc): https://github.com/andyfeili/CVE-2018-9276
- CVE-2018-9276 PRTG < 18.2.39 Reverse Shell (Python3 support) (github_poc): https://github.com/alvinsmith-eroad/CVE-2018-9276
- Python Exploit for CVE: 2018-9276 (github_poc): https://github.com/AC8999/PRTG-Network-Monitor-18.2.38---Authenticated-Remote-Code-Execution-CVE-2018-9276

## Other vulnerabilities in n/a

- [CVE-2018-19410](https://insights.sbomify.com/CVE-2018-19410/): Paessler PRTG Network Monitor Local File Inclusion (critical 9.8, exploited in the wild)
- [CVE-2020-10374](https://insights.sbomify.com/CVE-2020-10374/): Command injection in n/a (critical 9.8)
- [CVE-2023-51630](https://insights.sbomify.com/CVE-2023-51630/): Paessler PRTG Network Monitor Cross-Site Scripting Authentication Bypass Vulnerability (high 8.8)
- [CVE-2023-31452](https://insights.sbomify.com/CVE-2023-31452/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2018-19411](https://insights.sbomify.com/CVE-2018-19411/): Privilege escalation in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-9276 and fix it if it is affected.

What it is: CVE-2018-9276 is a high-severity command injection vulnerability in n/a, published on 2 Jul 2018. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2018-9276 in the wild since at least 4 Feb 2025.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-9276/ (Markdown: https://insights.sbomify.com/CVE-2018-9276/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-9276
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-9276
- OSV: https://osv.dev/vulnerability/CVE-2018-9276

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-9276/
Summaries are generated and may contain mistakes; the official description above is the record.