CVE-2020-10374
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 · uneditedA webserver component in Paessler PRTG Network Monitor 19.2.50 to PRTG 20.1.56 allows unauthenticated remote command execution via a crafted POST request or the what parameter of the screenshot function in the Contact Support form.
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 confidencePaessler PRTG Network Monitor versions 19.2.50 through 20.1.56 contain an unauthenticated remote command execution vulnerability in the webserver component. Attackers can exploit this via a crafted POST request or by manipulating the 'what' parameter in the screenshot function of the Contact Support form, allowing execution of arbitrary operating system commands without credentials.
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.2.50, <= 20.1.56CVSS 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.
-
Identify PRTG versionLocate the installed PRTG Network Monitor version number in the system information or about page of the PRTG admin interface, or check the version reported in the installer or service propertiesAffected if The installed version falls within the range 19.2.50 through 20.1.56 (inclusive)
-
Determine web interface exposureVerify whether the PRTG web server (typically on port 80 or 443) is accessible from untrusted networks or the internet without VPN or firewall restrictionsAffected if The PRTG web interface is exposed to unauthenticated network access from outside the trusted network
-
Assess Contact Support form accessibilityCheck if the Contact Support form endpoint is reachable without authentication by attempting to access the support contact page or reviewing web server access patternsAffected if The Contact Support form is accessible to unauthenticated users
-
Review web server logs for exploitation attemptsExamine PRTG web server logs for POST requests to the screenshot function or Contact Support endpoint with unusual or suspicious 'what' parameter values that may indicate command injectionAffected if Logs show POST requests with manipulated 'what' parameters or similar suspicious patterns to the Contact Support form
A user is affected if PRTG version is between 19.2.50 and 20.1.56 AND the web interface or Contact Support form is accessible to unauthenticated attackers.
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 · scopedUpdate PRTG Network Monitor to a version after 20.1.56 (or latest stable). Until patched, restrict network access to the PRTG web interface using firewall rules or VPN, and disable the Contact Support form if possible.
PRTG Network Monitor 20.1.57 or later
- Upgrade PRTG Network Monitor to version 20.1.57 or later (including any subsequent stable releases)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation3.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,440.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-10374 — 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-2020-10374 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