CVE-2017-12879
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 · uneditedCross-site scripting (XSS-STORED) vulnerability in the DEVICES OR SENSORS functionality in Paessler PRTG Network Monitor before 17.3.33.2654 allows authenticated remote attackers to inject arbitrary web script or HTML.
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 confidenceA stored cross-site scripting (XSS) vulnerability exists in the DEVICES OR SENSORS functionality of Paessler PRTG Network Monitor versions prior to 17.3.33.2654. Authenticated remote attackers can inject malicious web scripts or HTML into device or sensor names/parameters, which persist and execute when other authenticated users view the affected interfaces.
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<= 17.3.33CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/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 Network Monitor versionLocate the installed PRTG version via the web interface (typically in Setup > About > Version) or check the installation directory for version information filesAffected if Installed version is 17.3.33 or lower (any version prior to 17.3.33.2654)
-
Access Devices overviewLog into PRTG web interface and navigate to the Devices view to enumerate all registered devicesAffected if You have authenticated access to the PRTG interface
-
Inspect device names for suspicious contentReview each device's name field for unexpected characters such as <script>, javascript:, onload, onerror, or other HTML/JavaScript patternsAffected if Any device name contains HTML tags or script-related keywords
-
Inspect sensor names and parametersNavigate to individual sensors under each device and review the sensor names, as well as any configured parameters or tags for injected contentAffected if Any sensor name or parameter contains script tags or HTML attributes
-
Review sensor configuration pagesAccess the configuration page of individual sensors and examine fields such as sensor name, channel names, and tags for XSS payload patternsAffected if Sensor configuration fields contain encoded or raw script injection attempts
You are affected if running PRTG version 17.3.33 or lower AND any device or sensor name contains malicious script or HTML content that you did not intentionally configure.
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 dataUpgrade Paessler PRTG Network Monitor to version 17.3.33.2654 or later. As a compensating control, restrict administrative access and review existing device/sensor configurations for malicious input.
- 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-2017-12879 — 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-2017-12879 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