CVE-2018-14683
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 before 19.1.49.1966 has Cross Site Scripting (XSS) in the WEBGUI.
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 · moderate confidencePRTG Network Monitor versions prior to 19.1.49.1966 contain a Cross Site Scripting (XSS) vulnerability in its web interface (WEBGUI). The vulnerability allows attackers to inject malicious scripts through the web interface, potentially compromising other users' sessions or performing actions on their behalf.
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< 19.1.49.1966CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
-
Check PRTG version in web interfaceLog into the PRTG web interface using administrative credentials and locate the version number displayed in the footer of any page. The version format typically appears as '19.x.x.x' or similar.Affected if The displayed version number is less than 19.1.49.1966 (for example, 18.x.x.x or 19.1.48.x)
-
Check version via PRTG Administration toolOn the server hosting PRTG, open the PRTG Administration tool (usually accessible from the Start menu or system tray). Navigate to the 'About' or 'System Status' section to view the exact installed version.Affected if The version shown is below 19.1.49.1966
-
Verify web interface is accessibleConfirm that the PRTG web interface (WEBGUI) is enabled and reachable. This can be done by accessing the PRTG URL in a browser (commonly port 443 or 8080) or by checking the web server configuration in PRTG Administration tool under 'Web Server' settings.Affected if The web interface is enabled and accessible from a network where potential attackers could reach it, which is required for the XSS to be exploitable
-
Confirm PRTG core server is runningVerify the PRTG Core Service is running on the server. This can be checked via Windows Services (services.msc) looking for 'PRTG Core Service' or using the PRTG Administration tool status screen.Affected if The PRTG core service is running and the web interface is active, making the XSS vulnerability reachable
You are affected if your installed PRTG Network Monitor version is less than 19.1.49.1966 and the web interface is enabled and accessible.
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.
From vendor data19.1.49.1966
Upgrade PRTG Network Monitor to version 19.1.49.1966 or later. As an interim measure, implement content security policy headers and ensure users access the interface only from trusted networks to reduce exposure.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-14683 — 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-14683 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