CVE-2018-19410
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedPRTG 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).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencePRTG Network Monitor before 18.2.40.1683 contains a critical authentication bypass vulnerability where unauthenticated attackers can craft HTTP requests to override the 'include' directive in /public/login.htm, enabling Local File Inclusion to execute /api/addusers. This allows remote attackers to create administrative users with read-write privileges via the 'id' and 'users' parameters.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 18.2.40.1683CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify PRTG Network Monitor is installedCheck for PRTG installation by looking in Program Files for 'PRTG Network Monitor' folder, or check Windows Services for 'PRTG' services, or access the web interface on port 80/443Affected if PRTG Network Monitor is found on the system
-
Determine installed PRTG versionOpen the PRTG web interface and check the version displayed on the login page or in 'Setup' > 'System Administration' > 'About PRTG', or check the version in the program's executable propertiesAffected if The version number is lower than 18.2.40.1683
-
Inspect for unauthorized user accountsLog into PRTG as an administrator, navigate to 'Setup' > 'Account Settings' > 'User Management' or 'Users', and review all accounts for unknown or suspicious usernames with Administrator or Read-Write privilegesAffected if There are user accounts that were not created by your organization or that have elevated privileges you did not assign
-
Check network exposure of PRTG web interfaceDetermine if the PRTG web server (ports 80, 443, or configured custom ports) is accessible from untrusted networks by reviewing firewall rules or performing a port scan from an external IPAffected if The PRTG web interface is accessible from the internet or untrusted networks without IP restrictions
You are affected if PRTG Network Monitor is installed with a version lower than 18.2.40.1683 and the web interface is network-accessible, or if unauthorized administrator accounts exist in the system.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped18.2.40.1683
Upgrade PRTG Network Monitor to version 18.2.40.1683 or later. If immediate patching is not possible, restrict network access to the PRTG interface to trusted IPs only as a temporary compensating control.
18.2.40.1683
- 1. Download PRTG Network Monitor version 18.2.40.1683 or later from the official Paessler website (www.paessler.com)
- 2. Back up the current PRTG configuration, database, and settings before performing the upgrade
- 3. Install or upgrade to version 18.2.40.1683 following the vendor's standard upgrade procedure
- 4. After upgrade, verify the new version is running by checking the PRTG web interface
- 5. Confirm that the /public/login.htm vulnerability is no longer exploitable
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-19410 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-19410 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data