dbcve.org
ScreenconnectApplication · Connectwise

CVE-2025-14265

CRITICAL · 9.1 CVSS v3.1 Published 2025-12-11
Fix available
A fix is available. Upgrade to 25.8.0.9438 or later.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In versions of ScreenConnect™ prior to 25.8, server-side validation and integrity checks within the extension subsystem could allow the installation and execution of untrusted or arbitrary extensions by authorized or administrative users. Abuse of this behavior could result in the execution of custom code on the server or unauthorized access to application configuration data. This issue affects only the ScreenConnect server component; host and guest clients are not impacted. ScreenConnect 25.8 introduces enhanced server-side configuration handling and integrity checks to ensure only trusted extensions can be installed.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

ScreenConnect versions prior to 25.8 contain insufficient server-side validation and integrity checks in the extension subsystem. Authenticated administrative users can install untrusted or malicious extensions, leading to arbitrary code execution on the server or unauthorized access to sensitive application configuration data.

MitigationUpgrade ScreenConnect to version 25.8 or later, which implements enhanced server-side configuration handling and integrity verification for the extension subsystem.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ScreenconnectApplication
Affected:< 25.8.0.9438

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check ScreenConnect version via web interface
    Log into the ScreenConnect web portal as an administrator and navigate to the Setup or About page. The version number is typically displayed on the login page footer or in the Administration > Dashboard section.
    Affected if The displayed version is earlier than 25.8.0.9438 (e.g., 25.7.x, 25.6.x, earlier releases)
  2. Check version in web.config file
    Locate the web.config file in the ScreenConnect installation directory (commonly in C:\Program Files\ScreenConnect\ or /opt/screenconnect/). Open it and search for 'version' or 'AppVersion' entries.
    Affected if The version tag shows a build number lower than 25.8.0.9438
  3. Check version via Windows Registry (if Windows host)
    Open Registry Editor and navigate to HKLM\SOFTWARE\ScreenConnect\ or HKLM\SOFTWARE\Wow6432Node\ScreenConnect\. Look for a Version or InstallVersion string value.
    Affected if The registry version value is less than 25.8.0.9438
  4. Verify administrative user access to extension subsystem
    Confirm that the ScreenConnect installation has administrative-level user accounts configured and that the web interface is accessible. Navigate to Administration > Extensions or similar extension management page.
    Affected if Administrative users exist and the extension management interface is accessible (this condition enables exploitation)
  5. Check for installed extensions
    In the web interface, go to the Extensions page (Administration > Extensions) and list all currently installed extensions.
    Affected if Any extensions are installed - the vulnerability allows installation of untrusted/malicious extensions via this interface

You are affected if your ScreenConnect version is earlier than 25.8.0.9438 AND you have administrative users who can access the extension management subsystem.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 25.8.0.9438 or later
Fixed in 25.8.0.9438
Interim mitigation

Upgrade ScreenConnect to version 25.8 or later, which implements enhanced server-side configuration handling and integrity verification for the extension subsystem.

Recommended fix High confidence

ScreenConnect 25.8.0.9438 or later (25.8.x series)

  1. 1. Back up your current ScreenConnect installation and database before proceeding with the upgrade
  2. 2. Download ScreenConnect version 25.8.0.9438 or later from the official ConnectWise/ScreenConnect download portal
  3. 3. Apply the upgrade to your ScreenConnect server following ConnectWise's standard upgrade procedures
  4. 4. Verify the upgrade was successful by checking the server version in the administration interface
  5. 5. Review extension settings to ensure only trusted extensions are installed after the upgrade
Caveat The description does not indicate breaking changes; the upgrade focuses on security enhancements to the extension subsystem

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Screenconnect Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14265 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-14265 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data