Raw vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2023-32782 is a high-severity Command Injection (CWE-77) vulnerability in Paessler Prtg Network Monitor. Its CVSS base score is 7.2 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked in the top 1% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2023-32782 is a command injection vulnerability, tracked under CWE-77, that affects the Dicom C-ECHO sensor in Paessler PRTG Network Monitor 23.2.84.1566 and earlier releases. The flaw allows an authenticated user with write permissions to misuse the sensor's debug option, resulting in the creation of new files that can subsequently be executed through the EXE/Script sensor. It carries a CVSS 3.1 base score of 7.2 with a network attack vector, low complexity, and high impact on confidentiality, integrity, and availability.
An attacker who already possesses the required account privileges can leverage the debug functionality to inject commands that write arbitrary files to the system. These files may then be invoked by the EXE/Script sensor, enabling the attacker to execute code and achieve full control over affected monitoring instances.
Paessler addressed the issue, along with other vulnerabilities, in PRTG version 23.3.86.1520. The vendor's knowledge base article and release history page recommend upgrading to the patched build to eliminate the exposure. The associated EPSS score has remained flat at 0.2563 with no material increase since disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-37005
Vulnerability Data
A command injection was identified in PRTG 23.2.84.1566 and earlier versions in the Dicom C-ECHO sensor where an authenticated user with write permissions could abuse the debug option to write new files that could potentially get executed by the EXE/Script…
more
sensor. The severity of this vulnerability is high and received a score of 7.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.2.3V1.2.5V1.2.8V1.2.9
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require input validation and neutralization that prevent command injection.
Runtime monitoring of software and data can detect anomalous command execution resulting from injection.
Identifying recorded vulnerabilities enables remediation of command-injection flaws before exploitation.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure coding standards require proper escaping and parameterization of commands, directly eliminating CWE-77.
Security testing in development catches command-injection vulnerabilities before release.
Secure development life cycle mandates input validation and command construction practices that directly prevent command injection.
Application security requirements explicitly call for controls against injection flaws including command injection.
Secure architecture principles reduce the attack surface but do not prescribe the specific neutralization techniques needed.
Environment separation limits the blast radius of an exploited command injection but does not prevent the flaw itself.