Live › vulnerability › CVE-2025-3935
Go to dashboardConnectWise ScreenConnect has an improper authentication flaw that allows ViewState code injection, which can lead to remote code execution if machine keys are compromised. CISA lists it as actively exploited in the wild.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:11 UTC, 3h before NVD. All times on this page are UTC.
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| connectwise screenconnect | vendor | < 25.2.4 | 25.2.4 |
| ConnectWise ScreenConnect | vendor | – | – |
Unknown from the sources.
Apply mitigations per vendor instructions, or discontinue use of the product if mitigations are unavailable (per CISA required action).
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2025-3935")
CISA KEV catalog, Creative Commons 0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.