Connectwise Control
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in Connectwise Control.
By the Year
In 2026 there have been 0 vulnerabilities in Connectwise Control. Control did not have any published security vulnerabilities last year.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2026 | 0 | 0.00 |
| 2025 | 0 | 0.00 |
| 2024 | 0 | 0.00 |
| 2023 | 2 | 9.30 |
| 2022 | 0 | 0.00 |
| 2021 | 0 | 0.00 |
| 2020 | 6 | 7.07 |
It may take a day or so for new Control vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Connectwise Control Security Vulnerabilities
ConnectWise Control <22.9.10032: Reflected Param Injection via h
CVE-2023-25719
8.8 - High
- February 13, 2023
ConnectWise Control before 22.9.10032 (formerly known as ScreenConnect) fails to validate user-supplied parameters such as the Bin/ConnectWiseControl.Client.exe h parameter. This results in reflected data and injection of malicious code into a downloaded executable. The executable can be used to execute malicious queries or as a denial-of-service vector. NOTE: this CVE Record is only about the parameters, such as the h parameter (this CVE Record is not about the separate issue of signed executable files that are supposed to have unique configurations across customers' installations).
Injection
ConnectWise Control <=22.9.10032 Code Signing Bypass via Post-Sign Instructions
CVE-2023-25718
9.8 - Critical
- February 13, 2023
In ConnectWise Control through 22.9.10032 (formerly known as ScreenConnect), after an executable file is signed, additional instructions can be added without invalidating the signature, such as instructions that result in offering the end user a (different) attacker-controlled executable file. It is plausible that the end user may allow the download and execution of this file to proceed. There are ConnectWise Control configuration options that add mitigations.
Improper Verification of Cryptographic Signature
An issue was discovered in ConnectWise Control (formerly known as ScreenConnect) 19.3.25270.7185
CVE-2019-16512
4.8 - Medium
- January 23, 2020
An issue was discovered in ConnectWise Control (formerly known as ScreenConnect) 19.3.25270.7185. There is stored XSS in the Appearance modifier.
XSS
An issue was discovered in ConnectWise Control (formerly known as ScreenConnect) 19.3.25270.7185
CVE-2019-16513
8.8 - High
- January 23, 2020
An issue was discovered in ConnectWise Control (formerly known as ScreenConnect) 19.3.25270.7185. CSRF can be used to send API requests.
Session Riding
An issue was discovered in ConnectWise Control (formerly known as ScreenConnect) 19.3.25270.7185
CVE-2019-16514
7.2 - High
- January 23, 2020
An issue was discovered in ConnectWise Control (formerly known as ScreenConnect) 19.3.25270.7185. The server allows remote code execution. Administrative users could upload an unsigned extension ZIP file containing executable code that is subsequently executed by the server.
Unrestricted File Upload
An issue was discovered in ConnectWise Control (formerly known as ScreenConnect) 19.3.25270.7185
CVE-2019-16515
6.5 - Medium
- January 23, 2020
An issue was discovered in ConnectWise Control (formerly known as ScreenConnect) 19.3.25270.7185. Certain HTTP security headers are not used.
An issue was discovered in ConnectWise Control (formerly known as ScreenConnect) 19.3.25270.7185
CVE-2019-16516
5.3 - Medium
- January 23, 2020
An issue was discovered in ConnectWise Control (formerly known as ScreenConnect) 19.3.25270.7185. There is a user enumeration vulnerability, allowing an unauthenticated attacker to determine with certainty if an account exists for a given username.
Side Channel Attack
An issue was discovered in ConnectWise Control (formerly known as ScreenConnect) 19.3.25270.7185
CVE-2019-16517
9.8 - Critical
- January 23, 2020
An issue was discovered in ConnectWise Control (formerly known as ScreenConnect) 19.3.25270.7185. There is a CORS misconfiguration, which reflected the Origin provided by incoming requests. This allowed JavaScript running on any domain to interact with the server APIs and perform administrative actions, without the victim's knowledge.
Origin Validation Error
Stay on top of Security Vulnerabilities
Want an email whenever new vulnerabilities are published for Connectwise Control or by Connectwise? Click the Watch button to subscribe.