CVE-2019-16517 json
An issue was discovered in ConnectWise Control (formerly known as ScreenConnect) 19.3.25270.7185.
published 2020-01-23 6 y ago modified 2026-06-17 4 mo ago also EUVD-2019-7194
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 71%
- public exploits
- 0
- none known
Summary
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.
Exploit prediction
1.36% chance of exploitation in the next 30 days, higher than 71% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- know.bishopfox.com https://know.bishopfox.com/advisories/connectwise-control referenced PoC, tagged "exploit" by a source, unverified
- blog.huntresslabs.com https://blog.huntresslabs.com/validating-the-bishop-fox-findings-in-connectwise-control-9155eec36a34 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-346 Origin Validation Error
References
-
know.bishopfox.com
/advisories/connectwise-control
exploit, third-party-advisory
-
blog.huntresslabs.com
/validating-the-bishop-fox-findings-in-connectwise-control-9155eec36a34
exploit, third-party-advisory
-
know.bishopfox.com
/advisories
third-party-advisory
-
crn.com
/news/managed-services/connectwise-control-msp-security-vulnerabilities-are-severe-bishop-fox
third-party-advisory
-
crn.com
/slide-shows/managed-services/connectwise-control-attack-chain-exploit-20-questions-for-security-researcher-bi
third-party-advisory
Sources
- CVE List CVE-2019-16517
- NVD CVE-2019-16517
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.