VulnerabilityPublished 18 Dec 2025

CVE-2025-14823: ConnectWise ScreenConnect · Insertion of Sensitive Information Into Sent Data

Affects ConnectWise ScreenConnectSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium : upgrade to 1.0.12 when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.0.12

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade ConnectWise ScreenConnect to 1.0.12.

Affected software

Product	Affected	Fixed in
ConnectWise ScreenConnect	Affected <1.0.12	Fixed in 1.0.12

AI-suggested

European organizations using ConnectWise ScreenConnect with the Certificate Signing Extension should immediately update the extension to version 1.0.12 or later to ensure all sensitive configuration handling occurs server-side, preventing encrypted data exposure. Additionally, organizations should audit their deployment configurations to verify no legacy versions remain in use. Network-level controls such as restricting access to the ScreenConnect client-facing endpoints to trusted IP ranges can reduce exposure risk. Monitoring and logging client endpoint requests for unusual access patterns may help detect exploitation attempts. Organizations should also review their Azure Key Vault usage and rotate keys if there is suspicion of compromise. Implementing strict access controls and multi-factor authentication on management consoles further reduces risk. Finally, maintaining an up-to-date inventory of remote access tools and their extensions will aid in timely patch management.

Description

CVE-2025-14823 is a medium severity vulnerability in ConnectWise ScreenConnect when used with the Certificate Signing Extension versions prior to 1.0.12. It involves the unintended exposure of encrypted configuration values, including an Azure Key Vault-related key, to unauthenticated users via a client-facing endpoint. Although the sensitive data remains encrypted and secure at rest, its encrypted form could be leaked in client responses. Exploitation does not require authentication or user interaction, but the impact is limited to confidentiality as integrity and availability are unaffected. Updating the Certificate Signing Extension to version 1.0.12 or higher mitigates the issue by ensuring configuration handling is performed solely on the server side, preventing encrypted values from being sent to clients. European organizations using ScreenConnect with the vulnerable extension should prioritize patching to avoid potential information disclosure.

Impact

For European organizations, the primary impact of CVE-2025-14823 is the potential leakage of encrypted sensitive configuration data, including Azure Key Vault-related keys, to unauthenticated external actors. Although the data remains encrypted, repeated collection of encrypted values could aid attackers in cryptanalysis or facilitate further attacks if combined with other vulnerabilities. This could undermine the confidentiality of critical secrets used in remote support and management operations. Organizations relying on ConnectWise ScreenConnect for remote access, especially those integrating with Azure Key Vault for secret management, face increased risk of information disclosure. The vulnerability does not affect system integrity or availability, so operational disruption is unlikely. However, the exposure of encrypted secrets could lead to reputational damage, compliance issues under GDPR, and potential escalation if attackers leverage the leaked data in chained attacks. European entities in sectors with stringent data protection requirements, such as finance, healthcare, and government, should be particularly vigilant.

CWE-201Insertion of Sensitive Information Into Sent Data (opens in a new tab)
Base weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.
Requirements
Specify which data in the software should be regarded as sensitive. Consider which types of users should have access to which types of data.
Implementation
Ensure that any possibly sensitive data specified in the requirements is verified with designers to ensure that it is either a calculated risk or mitigated elsewhere.
System Configuration
Setup default error messages so that unexpected errors do not disclose sensitive information.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Choosing Message Identifier (opens in a new tab)
Exploiting Incorrectly Configured SSL/TLS (opens in a new tab)
WiFi MAC Address Tracking (opens in a new tab)
WiFi SSID Tracking (opens in a new tab)
Cellular Broadcast Message Request (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

connectwise.com/company/trust/security-bulletins/2025-12-18-screenconnect-certificate-signing-extension-update (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 25 Dec 2025, 16:35 UTC

WeaknessesCWE-201

Technical details

References

Community reviews

Related threats