ConnectWise / Control
8 CVEs
| CVE ID | Description | Severity | CVSS | Published |
|---|---|---|---|---|
| CVE-2023-25719 | ConnectWise Control before 22.9.10032 (formerly known as ScreenConnect) fails to validate user-supplied parameters such as the Bin/ConnectWiseControl.Client.ex… | HIGH | 8.8 | Feb 13, 2023 |
| CVE-2023-25718 | In ConnectWise Control through 22.9.10032 (formerly known as ScreenConnect), after an executable file is signed, additional instructions can be added without i… | CRITICAL | 9.8 | Feb 13, 2023 |
| CVE-2019-16515 | An issue was discovered in ConnectWise Control (formerly known as ScreenConnect) 19.3.25270.7185. Certain HTTP security headers are not used. | MEDIUM | 6.5 | Jan 23, 2020 |
| CVE-2019-16516 | An issue was discovered in ConnectWise Control (formerly known as ScreenConnect) 19.3.25270.7185. There is a user enumeration vulnerability, allowing an unauth… | MEDIUM | 5.3 | Jan 23, 2020 |
| CVE-2019-16514 | An issue was discovered in ConnectWise Control (formerly known as ScreenConnect) 19.3.25270.7185. The server allows remote code execution. Administrative users… | HIGH | 7.2 | Jan 23, 2020 |
| CVE-2019-16517 | An issue was discovered in ConnectWise Control (formerly known as ScreenConnect) 19.3.25270.7185. There is a CORS misconfiguration, which reflected the Origin… | CRITICAL | 9.8 | Jan 23, 2020 |
| CVE-2019-16512 | An issue was discovered in ConnectWise Control (formerly known as ScreenConnect) 19.3.25270.7185. There is stored XSS in the Appearance modifier. | MEDIUM | 4.8 | Jan 23, 2020 |
| CVE-2019-16513 | An issue was discovered in ConnectWise Control (formerly known as ScreenConnect) 19.3.25270.7185. CSRF can be used to send API requests. | HIGH | 8.8 | Jan 23, 2020 |
Showing 1 to 8 of 8 CVEs