Description
ScreenConnect versions 25.2.3 and earlier versions may be susceptible to a ViewState code injection attack. ASP.NET Web Forms use ViewState to preserve page and control state, with data encoded using Base64 protected by machine keys. It is important to note that to obtain these machine keys, privileged system level access must be obtained.If these machine keys are compromised, attackers could create and send a malicious ViewState to the website, potentially leading to remote code execution on the server. The risk does not originate from a vulnerability introduced by ScreenConnect, but from platform level behavior. This had no direct impact to ScreenConnect Client. ScreenConnect 2025.4 patch disables ViewState and removes any dependency on it.
CVSS scores
| Version | Scored by | Score | Vector |
|---|---|---|---|
| CVSS 3.1 | ConnectWise (CNA) | 8.1 High | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CVSS 3.1 | NVD (NIST) | 7.2 High | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
Timeline
- CVE published
- Added to CISA KEV (exploited in the wild)
- CISA remediation deadline (passed)
- Last updated by the CVE authority
- First tracked by SecureCyberVM
Exploit likelihood (EPSS)
Exploitation
- Listed in the CISA Known Exploited Vulnerabilities catalog on 2025-06-02.
- U.S. federal remediation due date: 2025-06-23.
Am I affected?
- Do you run ConnectWise ScreenConnect? Check the exact versions in the affected products list.
- Is the affected service reachable from the internet or by untrusted users? Exposed systems come first.
- It is actively exploited: assume attackers are scanning for it and look for indicators of compromise on exposed systems.
- Apply the fix below, or the workaround if you cannot patch yet, then confirm the new version is running.
Affected products
- ConnectWise ScreenConnect: <25.2.3 · All ConnectWise vulnerabilities
Fix
Cloud: No action is required.On-premises: Upgrade to the latest stable version.Details and guidance can be found here:ScreenConnect 25.2.4 Security Patch https://www.connectwise.com/company/trust/security-bulletins/screenconnect-security-patch-2025.4
Mitigations
- CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Weakness
CWE-502 Deserialization of Untrusted Data
Coverage of CVE-2025-3935
Other ConnectWise vulnerabilities
- CVE-2026-84869 Exploited ConnectWise ScreenConnect Improper Privilege Management and Missing Authorization Vulnerab
- CVE-2024-1708 Exploited ConnectWise ScreenConnect Path Traversal Vulnerability
- CVE-2024-1709 Exploited ConnectWise ScreenConnect Authentication Bypass Vulnerability
All ConnectWise vulnerabilities →
Frequently asked questions
Is CVE-2025-3935 being actively exploited?
Yes. CISA added CVE-2025-3935 to its Known Exploited Vulnerabilities catalog on 2025-06-02, which means attackers are using it in real attacks. US federal agencies must fix it by 2025-06-23.
How severe is CVE-2025-3935?
CVE-2025-3935 has a highest CVSS score of 8.1 (High) under CVSS 3.1. Severity alone is not priority: check exploitation status and whether you run an affected version.
How do I fix CVE-2025-3935?
Cloud: No action is required. On-premises: Upgrade to the latest stable version. Details and guidance can be found here: ScreenConnect 25.2.4 Security Patch https://www.connectwise.com/company/trust/security-bulletins/screenconnect-security-patch-2025.4
Which products are affected by CVE-2025-3935?
ConnectWise ScreenConnect. See the affected products list on this page for exact versions.
References
- https://www.connectwise.com/company/trust/security-bulletins/screenconnect-security-patch-2025.4
- https://www.connectwise.com/company/trust/advisories
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-3935
Change log
- First recorded on SecureCyberVM from CVE.org, NVD, CISA KEV and FIRST EPSS.
Sources: CVE.org, NIST NVD, CISA KEV and ADP, FIRST EPSS. This record is refreshed automatically every day; changes are listed in the change log above.
