SecOps SignalSecurity Intelligence Workspace
Loading collection status
Vulnerabilities/CVE-2025-3935Public Intelligence Dossier
Source: connectwise · Limited verification•Last verified: •Collection Degraded
CVE-2025-3935ListedHIGH (raw)CVSS 8.1CWE-502

ScreenConnect versions 25.2.3 and earlier versions may be susceptible to a ViewState code injection attack

Published: 26 Apr 2025•Last updated: 17 Jun 2026, 02:50 PM IST•Source identifier: 7d616e1a-3288-43b1-a0dd-0a65d3e70a49
Dossier completeness: source-provided sections 3 / 3 · rule guidance available. Missing source facts count as incomplete.
Official source
CISA KEV catalog
Listed
Added02 Jun 2025
Due23 Jun 2025
RansomwareUnknown
CVSS score
8.1HIGH (raw)
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Metric source7d616e1a-3288-43b1-a0dd-0a65d3e70a49
EPSS probability
3.6%0.036
Percentile89th
Weakness type
CWE-502
No further CWE recorded
Remediation
Patch status unknown
No fixed version or KB recorded

Why It Matters

Analysis dossier

Why It Matters

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.

SOC priority

Immediate Attention

Actively exploited (source statement)

Yes

Publicly disclosed

Unknown

Risk basis: CISA KEV exploitation signal; HIGH severity; Known exploitation signal from CISA KEV or ransomware metadata; Source-confirmed exploitation or CISA KEV/ransomware metadata

Affected Products & Remediation

1 source-backed product
Affected products and versions (source)
  • connectwise screenconnect · < 25.2.4 · NVD CPE · Source
Recorded patch / KBNot provided by source

Vendor or catalog guidance (source)

  • CISA KEV: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Known exploitation (source facts)

Only what a source states. Unknown means no source has said either way; it is not "not exploited".

CISA KEV
Listed
Exploited (source statement)
Yes
Publicly disclosed (source)
Unknown

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.

Suggested hunting (rule-based inference)

SecOps Signal recommendation (rule-based inference). These steps are hunting hypotheses from the vulnerability class; they do not state or imply that exploitation occurred here or anywhere.

Matched kev-network-exposure (CVSS AV:N, CISA KEV Listed); deserialization (CWE-502)

Exposure

  1. Identify assets with the exact CVE and confirm the affected product/version against the advisory.Telemetry: DeviceTvmSoftwareVulnerabilities · KEV listing raises urgency, but inventory is needed to establish local exposure. · Rule kev-network-exposure
  2. Find installations of the affected component and confirm the source-stated version range.Telemetry: Application inventory · Deserialization risk requires component and version evidence. · Rule deserialization

Exploitation evidence

  1. Review relevant edge or application access logs for unusual requests around the advisory window.Telemetry: CommonSecurityLog · Log review is a hunting hypothesis; KEV listing alone does not show local exploitation. · Rule kev-network-exposure
Show more (2)

Exploitation evidence

  1. Review unusual child processes or network connections from the affected service.Telemetry: DeviceProcessEvents · Unexpected behavior may support investigation but is not proof by itself. · Rule deserialization

Response

  1. Recheck the affected assets after the source-stated mitigation or update is applied.Telemetry: DeviceTvmSoftwareVulnerabilities · A follow-up inventory check verifies local remediation. · Rule kev-network-exposure

CISA KEV Record

Catalog entry
02 Jun 2025
Required action due
23 Jun 2025
Known ransomware use
Unknown

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Change History & Source Data

— No recorded material change

CNA / source
7d616e1a-3288-43b1-a0dd-0a65d3e70a49
Record status · verification
UPDATED · CISA KEV confirmed
CPE
cpe:2.3:a:connectwise:screenconnect:*:*:*:*:*:*:*:*

Linked by the query's stored exact CVE association. Review required tables and validation status before use.

Detection Hunting Query
Target: DeviceTvmSoftwareVulnerabilities•Defender XDR
Detect endpoints exposed to CVE-2025-3935
Purpose: Exposure assessment (Category: Exposure Check)Why linked: Query metadata names CVE-2025-3935
DeviceTvmSoftwareVulnerabilities| where CveId == "CVE-2025-3935"| project DeviceId, DeviceName, OSPlatform, OSVersion, SoftwareVendor, SoftwareName, SoftwareVersion, CveId, VulnerabilitySeverityLevel, RecommendedSecurityUpdate, RecommendedSecurityUpdateId| sort by VulnerabilitySeverityLevel desc
Schema Checked · Not runtime validatedSource: SecOps Signal deterministic template · Limited verificationStatic screening: Passed structure and schema checks; tenant execution is not verified.

Looking up related community queries…

Loading related intelligence

Correlated briefings

SecOps Signal surfaces public advisory facts only. A missing value means the source has not published it, not that your environment is unaffected. No tenant inventory is connected.