Security readout for executives and security teams
Plain-English summary
A remote, unauthenticated attacker could potentially take administrative control of a vulnerable vsDesk deployment. The reported flaw allows authentication to be redirected to an attacker-controlled LDAP service, enabling creation of a new administrator. Successful compromise could expose or alter all data managed through vsDesk and disrupt service availability.
Executive priority
Treat this as an urgent remediation item for any reachable vsDesk deployment. Prioritize asset discovery, temporary access restriction, administrator-account review, and a vendor-confirmed upgrade. The potential impact is full administrative compromise without prior credentials or user action.
Technical view
CVE-2025-14600 is described as insecure deserialization and classified under CWE-305. Manipulated configuration data can force vsDesk to use an arbitrary LDAP server and provision an administrative account. It has CVSS 4.0 score 9.3 with network access, low complexity, no privileges, and no user interaction. The title mentions path traversal, but the supplied description does not explain that mechanism.
Likely exposure
Internet-accessible or otherwise untrusted-network-accessible vsDesk instances are the primary concern because the vector indicates unauthenticated network exploitation. Versions 11.06.02 and 14.01.01 are listed as affected. Version 14.0402 is inconsistently identified as both affected and patched, so its status requires vendor confirmation.
Exploitation context
The supplied bundle does not identify public exploitation or inclusion in CISA's Known Exploited Vulnerabilities catalog. It establishes a plausible pre-authentication administrative takeover path, but provides no evidence about exploit availability, observed attacks, or exploitation reliability.
Researcher notes
The record contains material inconsistencies: its title says path traversal, its description says insecure deserialization, and its CWE identifies missing authentication. Version 14.0402 appears in both the affected list and the claimed patched range. Researchers should avoid inferring the precise root cause or fixed boundary until the vendor or advisory clarifies them.
Mitigation direction
- Identify every deployed vsDesk instance and its exact version and build.
- Obtain vendor confirmation of the first fixed build because version 14.0402 is reported inconsistently.
- Upgrade affected systems to a vendor-confirmed patched release as an urgent change.
- Restrict vsDesk network access to trusted users and management networks until remediation is verified.
- Review vendor guidance for additional mitigations or compromise indicators.
Validation and detection
- Confirm deployed versions against the vendor's authoritative fixed-version guidance.
- Verify configured LDAP endpoints and investigate unexpected or recently changed servers.
- Review administrator accounts for unexplained creation, privilege changes, or unfamiliar identities.
- Examine configuration and authentication records for unauthorized modifications or anomalous LDAP activity.
- After upgrading, verify the installed build and confirm normal authentication behavior.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-305: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-14600 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.3 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——KasperskyVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/klsecservices/Advisories/blob/master/KLSA-00296-Admin-Account-Takeover-via-Path-Traversal-in-vsDesk.mdCVE reference, Kaspersky
- https://vsdesk.ru/news/vyshla-novaya-versiya-140422CVE reference, Kaspersky
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authentication Bypass by Primary Weakness
Authentication Bypass by Primary Weakness represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.