Threats / Paessler / CVE-2018-19410
CVE-2018-19410
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Paessler PRTG Network Monitor vulnerability
Paessler PRTG Network Monitor contains a local file inclusion vulnerability allowing remote, unauthenticated attackers to create administrative users.
Verdict
Today item — known-exploited.
A remote unauthenticated attacker exploits local file inclusion to bypass authentication and gain administrative access to PRTG Network Monitor, enabling full system compromise and network monitoring infrastructure takeover.
CISA KEV Yes · 2025-02-044EPSS 0.8646 (verify live)5Exploit Weaponized · public PoC6CVSS 9.8 (CISA)3CISA SSVC Exploitation: active · Automatable: yes · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
197 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-02-04).
Probability (EPSS)
EPSS 0.8646 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: Paessler, PRTG Network Monitor. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 2267 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a public proof-of-concept / detection template). Catalog entries: nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious request exploiting the local file inclusion flaw to access sensitive configuration files without authentication.
Business
Network monitoring infrastructure becomes accessible to unauthorized parties, exposing sensitive operational data.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I leverage the file inclusion vulnerability to create new user accounts with administrator privileges.
Business
Attacker gains persistent administrative access to critical monitoring systems, enabling long-term control.
3
Lateral reach — past segmentation narrative 3
Attacker
I use the newly created administrative account to modify monitoring configurations, disable alerts, or exfiltrate network intelligence.
Business
Organization loses visibility into network health, security incidents go undetected, and competitive intelligence is compromised.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05