Kiteworks MFT up to 9.0.x incorrectly specified destination in a communication channel
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.8 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in Kiteworks MFT up to 9.0.x. This affects an unknown function. Such manipulation leads to incorrectly specified destination in a communication channel. This vulnerability is referenced as CVE-2025-53899. It is possible to launch the attack remotely. No exploit is available. The affected component should be upgraded.
Details
A vulnerability was found in Kiteworks MFT up to 9.0.x and classified as problematic. Affected by this issue is an unknown part. The manipulation with an unknown input leads to a incorrectly specified destination in a communication channel vulnerability. Using CWE to declare the problem leads to CWE-941. 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. Impacted is confidentiality, integrity, and availability. CVE summarizes:
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.
The advisory is available at github.com. This vulnerability is handled as CVE-2025-53899 since 07/11/2025. The exploitation is known to be easy. The attack may be launched remotely. The exploitation requires an enhanced level of successful authentication. The technical details are unknown and an exploit is not available.
Upgrading to version 9.1.0 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-199896). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.9VulDB Meta Temp Score: 5.8
VulDB Base Score: 4.7
VulDB Temp Score: 4.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.2
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Incorrectly specified destination in a communication channelCWE: CWE-941
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: MFT 9.1.0
Timeline
07/11/2025 CVE reserved11/29/2025 Advisory disclosed
11/29/2025 VulDB entry created
11/29/2025 VulDB entry last update
Sources
Advisory: GHSA-5gx5-vcpp-8cr5Status: Confirmed
CVE: CVE-2025-53899 (🔒)
GCVE (CVE): GCVE-0-2025-53899
GCVE (VulDB): GCVE-100-333770
EUVD: 🔒
Entry
Created: 11/29/2025 09:16Updated: 11/29/2025 10:31
Changes: 11/29/2025 09:16 (63), 11/29/2025 10:31 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.