Skip to content
vulnerability

CVE-2018-19410

9.8
Critical
KEV · Exploited in wildEPSS 98%

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).

exploited
Yes, in CISA KEV since 4 Feb 2025fix by 25 Feb 2025 (CISA deadline for US federal agencies)unvetted proof-of-concept code on github
fix
No fixed release stated by the publisher
likelihood
EPSS 97.9%
Published 21 Nov 2018Analysed here 2 Nov 2026CVSS scored by CISA

do firstApply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

triage
surface unknownruntimeWAF can block: partlyAV · network

Can a WAF block it? Partly. The attack is performed by sending a crafted HTTP request with specific parameters to a known endpoint, which is unusual and can be detected by a WAF rule matching these parameters and the endpoint path. A WAF rule can match 'id' and 'users' parameters in an HTTP request to /api/addusers. No tracked WAF vendor has published a rule for this CVE yet, so you would write it yourself.

What a custom rule would match: 'id' and 'users' parameters in an HTTP request to /api/addusers

Also consider: patch · custom WAF rule

Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

cvss vector
attack vectornetworkattack complexitylowprivileges requirednoneuser interactionnonescopeunchangedconfidentialityhighintegrityhighavailabilityhigh
CVSS 3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
common questions

Is CVE-2018-19410 being exploited?

Yes. CVE-2018-19410 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2018-19410?

CVE-2018-19410 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2018-19410?

Not known from our data. No patch reference has been recorded for CVE-2018-19410, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2018-19410 affect?

CVE-2018-19410 affects paessler:prtg_network_monitor. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
paessler:prtg_network_monitor

public exploits

Unvetted proof-of-concept code on GitHub: 1 GitHub proof of concept · 1 Nuclei template

Nuclei
GitHub proofs of concept

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

cisa ssvc

exploitation
active
automatable
yes
technical impact
total

Assessed by CISA 4 Feb 2025 (SSVC 2.0.3).

timeline

  1. 21 Nov 2018Published
  2. 25 Jan 2024First proof-of-concept repository on GitHub (unvetted) · 1,890 days (about 5 years) later
  3. 4 Feb 2025Added to CISA KEV (exploited in the wild) · 376 days (about 1 year) later
  4. 4 Feb 2025CISA SSVC assessment: exploitation active · 1 day later
  5. 25 Feb 2025CISA remediation due date (US federal agencies) · 20 days later
  6. 21 Oct 2025CVE record last updated · 239 days (about 8 months) later
  7. 2 Nov 2026Analysed by vulneraibility.com · 377 days (about 1 year) later
how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
2 references in the CVE record: 2 links
  • Linkptsecurity.com /ww-en/analytics/threatscape/pt-2018-24/
  • Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2018-19410

sources

get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved