CVE-2025-9650
BaseFortify
Publication date: 2025-08-29
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| yeqifu | carrental | * |
| yeqifu | carrental | 3fabb7eae93d209426638863980301d6f99866b3 |
| yeqifu | carrental | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-9650 is a path traversal vulnerability in the yeqifu carRental application. It occurs in the removeFileByPath function in the AppFileUtils.java file, where the input parameter 'carimg' is improperly handled. This allows an attacker to manipulate the file path to traverse directories outside the intended scope and delete arbitrary files on the server remotely. [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing an attacker to delete any file on the server remotely, which can lead to denial of service or severe damage to the system's integrity and availability. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection can focus on monitoring requests to the vulnerable interface `car/updateCar.action` that include the `carimg` parameter with suspicious path traversal patterns such as '../'. Network or web server logs can be searched for such patterns. For example, using grep on logs: `grep 'car/updateCar.action' /path/to/access.log | grep '\.\./'` to find attempts to exploit path traversal. Additionally, monitoring for unexpected file deletions on the server may indicate exploitation attempts. Since a public proof-of-concept exploit exists, scanning for known exploit payloads in traffic is recommended. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting or disabling access to the vulnerable `car/updateCar.action` interface if possible, applying input validation or sanitization on the `carimg` parameter to prevent path traversal sequences (e.g., removing '../'), and monitoring for exploitation attempts. Since no known countermeasures or patches are currently available, replacing or updating the affected component is suggested. Additionally, implementing strict access controls and limiting permissions on the server to minimize damage from potential exploitation is advised. [2]