CVE-2016-5078
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 · uneditedPaessler PRTG before 16.2.24.4045 has XSS via SNMP.
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 confidencePaessler PRTG Network Monitor before version 16.2.24.4045 contains a stored Cross-Site Scripting (XSS) vulnerability via the SNMP interface. Attackers can inject malicious JavaScript code through SNMP community strings or OID values that get reflected in the PRTG web interface without proper sanitization.
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<= 16.2.24.3791CVSS 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.
-
Verify PRTG Network Monitor versionAccess the web interface and check the version information (typically found in the footer or in Setup > System Administration > Server Settings), or check via the PRTG administration toolAffected if The installed version is 16.2.24.3791 or earlier (any version less than 16.2.24.4045)
-
Confirm SNMP interface is enabledCheck if any SNMP sensors are configured or if SNMP monitoring is active in the PRTG installationAffected if SNMP sensors or SNMP monitoring functionality is enabled and accessible to the attacker
-
Inspect configured SNMP community stringsReview SNMP sensor configurations or probe settings where community strings are defined - these are the values that could contain malicious injected codeAffected if SNMP community strings contain unsanitized user-supplied input that could include script tags
-
Examine SNMP OID values in sensorsReview the OID or object identifiers configured in any SNMP sensors for unexpected or injected contentAffected if OID values contain JavaScript code or script tags that would be reflected in the web interface
You are affected if running PRTG version 16.2.24.3791 or earlier AND the SNMP interface is configured with community strings or OID values that contain unescaped HTML/JavaScript characters.
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 PRTG Network Monitor to version 16.2.24.4045 or later. As a temporary measure, restrict SNMP access to trusted IPs and validate/sanitize all SNMP input before processing.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.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 $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-5078 — 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-2016-5078 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