CVE-2019-16513 json
An issue was discovered in ConnectWise Control (formerly known as ScreenConnect) 19.3.25270.7185.
published 6y ago modified 4mo ago also EUVD-2019-7190
- cvss
- 8.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 63%
- public exploits
- 0
- none known
Summary
An issue was discovered in ConnectWise Control (formerly known as ScreenConnect) 19.3.25270.7185. CSRF can be used to send API requests.
Is CVE-2019-16513 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.02% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-09).
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 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
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-16513
- NVD CVE-2019-16513
Fencer Intel 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.