dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-34181

HIGH · 8.7 CVSS v4.0 Published 2025-12-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/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
NetSupport Manager < 14.12.0001 contains an arbitrary file write vulnerability in its Connectivity Server/Gateway PUTFILE request handler. An attacker with a valid Gateway Key can supply a crafted filename containing directory traversal sequences to write files to arbitrary locations on the server. This can be leveraged to place attacker-controlled DLLs or executables in privileged paths and achieve remote code execution in the context of the NetSupport Manager connectivity service.

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

NetSupport Manager Connectivity Server/Gateway contains an arbitrary file write vulnerability in its PUTFILE request handler. Attackers with a valid Gateway Key can use directory traversal sequences (e.g., ../../) in crafted filenames to write files to arbitrary locations on the server file system, including privileged paths.

MitigationUpgrade to NetSupport Manager version 14.12.0001 or later. Until patched, restrict network access to the Gateway service and rotate any compromised Gateway Keys immediately.

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

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
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Identify if NetSupport Manager Gateway is installed
    Look for NetSupport Manager Gateway service or executable on the system. Check for service named 'NetSupport Manager Gateway' or look for installation in Program Files/NetSupport directories.
    Affected if NetSupport Manager Gateway service or executable is found on the system
  2. Check installed NetSupport Manager version
    Locate the NetSupport Manager Gateway executable (typically named nsm.exe or similar in the installation directory) and check its file version property, or query the installed software in Add/Remove Programs.
    Affected if The version is lower than 14.12.0001 (the patched version)
  3. Determine if Gateway service is running and exposed
    Check if the NetSupport Manager Gateway service is running (via Services.msc or command line 'sc query'). If running, verify network listeners using 'netstat -an | grep' on common Gateway ports (typically TCP ports 4655, 47055, or as configured).
    Affected if The Gateway service is running and listening on accessible network ports
  4. Check for Gateway Key configuration
    Locate the Gateway configuration file (typically gateway.key or similar in the NetSupport Manager config directory) that stores the Gateway Key used for authentication.
    Affected if A Gateway Key is configured and present on the system

The environment is affected if NetSupport Manager Gateway with a version lower than 14.12.0001 is installed, the Gateway service is running and network-accessible, and a valid Gateway Key exists for authentication.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to NetSupport Manager version 14.12.0001 or later. Until patched, restrict network access to the Gateway service and rotate any compromised Gateway Keys immediately.

Recommended fix High confidence

14.12.0001 or later

  1. Identify all systems running NetSupport Manager Connectivity Server/Gateway
  2. Check the current version of NetSupport Manager installed (look for version < 14.12.0001)
  3. Download NetSupport Manager version 14.12.0001 or later from the official NetSupport website or your organization's software distribution point
  4. Backup the current NetSupport Manager configuration before upgrading
  5. Apply the upgrade to the Connectivity Server/Gateway component following NetSupport's standard upgrade procedure
  6. Verify the upgrade was successful by confirming the version displays as 14.12.0001 or higher
  7. Consider rotating the Gateway Key as a precautionary measure since a valid key was required for this exploitation

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-34181 — 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-34181 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