security-advisories: Incorrectly Specified Destination in a Communication Channel
CVE-2025-53899 is a high-severity incorrectly specified destination in a communication channel vulnerability in security-advisories from Kiteworks, with a CVSS 3.1 base score of 7.2 out of 10. It can be exploited remotely over the network by an attacker with administrator privileges, without any action from a user. Affected security-advisories versions: < 9.1.0. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1% chance of exploitation within 30 days, higher than 63% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Kiteworks Managed File Transfer to 9.1.0 or a later version.
- Read the advisory on github.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Kiteworks | security-advisories | < 9.1.0 | Not stated |
| Accellion | Kiteworks Managed File Transfer | before 9.1.0 | 9.1.0 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- HighAdministrator-level access is required first.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (github.com).
Official description
Kiteworks MFT orchestrates end-to-end file transfer workflows. Prior to version 9.1.0, the back-end of Kiteworks MFT is vulnerable to an incorrectly specified destination in a communication channel which allows an attacker with administrative privileges on the system under certain circumstances to intercept upstream communication which could lead to an escalation of privileges. This issue has been patched in version 9.1.0.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Incorrectly Specified Destination in a Communication Channel
The product creates a communication channel to initiate an outgoing request to an actor, but it does not correctly specify the intended destination for that actor.
More Incorrectly Specified Destination in a Communication Channel vulnerabilities (CWE-941)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
- github.com/kiteworks/security-advisories/security/advisories/GHSA-5gx5-vcpp-8cr5Third Party Advisory
Other vulnerabilities in security-advisories
- 7.2 High severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
- 8.1 High severity
Recent Incorrectly Specified Destination in a Communication Channel vulnerabilities
- 7.5 High severity
Spotted an error? Tell us.