# CVE-2018-19410: Paessler PRTG Network Monitor Local File Inclusion

> Unauthenticated attackers can bypass authentication via Local File Inclusion to create administrator accounts, leading to full system compromise.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 4 Feb 2025 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Nov 2018
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-pm93-g4gf-j42f

## What is CVE-2018-19410?

CVE-2018-19410 is a critical authentication bypass vulnerability in n/a, published on 21 Nov 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PRTG Network Monitor before 18.2.40.1683 allows remote unauthenticated attackers to create users with read-write privileges (including administrator). A remote unauthenticated user can craft an HTTP request and override attributes of the 'include' directive in /public/login.htm and perform a Local File Inclusion attack, by including /api/addusers and executing it. By providing the 'id' and 'users' parameters, an unauthenticated attacker can create a user with read-write privileges (including administrator).

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

It affects 1 product.


Products: Paessler Prtg Network Monitor.

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

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

## Is CVE-2018-19410 being exploited?

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

Public exploit code:

- Proof of concept for the vulnerability CVE-2018-19410 (github_poc): https://github.com/himash/CVE-2018-19410-POC
- PRTG Network Monitor - Local File Inclusion (nuclei): http/cves/2018/CVE-2018-19410.yaml

## Other vulnerabilities in n/a

- [CVE-2018-9276](https://insights.sbomify.com/CVE-2018-9276/): Paessler PRTG Network Monitor OS Command Injection (high 7.2, 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-19410 and fix it if it is affected.

What it is: CVE-2018-19410 is a critical authentication bypass vulnerability in n/a, published on 21 Nov 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2018-19410 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-19410/ (Markdown: https://insights.sbomify.com/CVE-2018-19410/index.md)
```

## Sources

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

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