dbcve.org
PlatformApplication · 1e

CVE-2025-1683

HIGH · 7.8 CVSS v3.1 Published 2025-03-12
Fix available
A fix is available. Upgrade to 25.3 or later.
See remediation →
80/100
Remediation priority · High
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
Improper link resolution before file access in the Nomad module of the 1E Client, in versions prior to 25.3, enables an attacker with local unprivileged access on a Windows system to delete arbitrary files on the device by exploiting symbolic links.

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

A symlink vulnerability in the Nomad module of 1E Client versions prior to 25.3 allows local unprivileged attackers on Windows systems to delete arbitrary files by exploiting improper link resolution before file access. The attacker creates malicious symbolic links that the vulnerable software follows without proper validation.

MitigationUpgrade the 1E Client Nomad module to version 25.3 or later to obtain the patched binaries.

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
PlatformApplication
Affected:< 25.3

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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. Verify 1E Client Nomad module is installed
    Open Windows Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product' in PowerShell, and look for entries containing '1E Client' or 'Nomad'
    Affected if 1E Client with Nomad module is present on the system
  2. Identify the installed 1E Client version
    Check the version of the 1E Client installation - typically found in the program's properties in Programs and Features, or check the file version of the main executable (commonly in C:\Program Files\1E\ or similar location)
    Affected if The version displayed is earlier than 25.3 (e.g., 25.2.x, 24.x, etc.)
  3. Confirm Nomad module version specifically
    If version information is available per-module, check the version property of the Nomad component specifically - this may be visible in 1E Client's own UI, configuration tool, or installer details
    Affected if The Nomad module version is less than 25.3
  4. Verify symlink creation capability exists
    Confirm the Windows user account has permission to create symbolic links in any writable directory - run 'mklink testlink target' in a temp directory as the user in question
    Affected if The unprivileged user can create symbolic links on the system

If 1E Client with the Nomad module is installed and its version is earlier than 25.3, the environment is vulnerable to arbitrary file deletion via symlink attacks.

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.3 or later
Fixed in 25.3
Interim mitigation

Upgrade the 1E Client Nomad module to version 25.3 or later to obtain the patched binaries.

Recommended fix Moderate confidence

1E Client version 25.3

  1. Identify the current version of 1E Client installed on affected systems by checking Add/Remove Programs or the program's version information
  2. Download 1E Client version 25.3 or later from the official 1E or TeamViewer support website
  3. Test the upgrade in a non-production environment to ensure compatibility with existing systems
  4. Deploy the upgrade to production systems following standard change management procedures
  5. Verify the upgrade was successful by confirming the installed version is 25.3 or higher

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

Fix this in Platform Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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