CVE-2025-65878
BaseFortify
Publication date: 2025-12-05
Last updated on: 2025-12-12
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| yeqifu | warehouse_management_system | 1.2 |
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?
This vulnerability exists in the warehouse management system version 1.2, where the endpoint `/file/showImageByPath` does not properly sanitize user input in the path parameters. This allows an attacker to perform directory traversal attacks, enabling them to read arbitrary files on the server's file system.
How can this vulnerability impact me? :
Exploiting this vulnerability could allow an attacker to access sensitive system information stored on the server, potentially leading to information leakage and further attacks.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows attackers to read arbitrary files on the server, including sensitive system and credential-containing files. Such unauthorized disclosure of sensitive information could lead to non-compliance with data protection regulations like GDPR and HIPAA, which require safeguarding personal and sensitive data against unauthorized access and breaches. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by sending crafted HTTP GET requests to the /file/showImageByPath endpoint with path parameters containing directory traversal sequences such as "../". For example, you can use curl commands to attempt to read sensitive files like the Windows "win.ini" file. A sample command is: curl -v "http://<target-host>/file/showImageByPath?path=../../../windows/win.ini". If the server responds with the contents of the file and HTTP status 201, the vulnerability is present. Monitoring network traffic for such suspicious requests or responses with content type "application/octet-stream" from this endpoint can also help detect exploitation attempts. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include normalizing and canonicalizing the input path parameter to remove any directory traversal sequences, rejecting any paths containing ".." or absolute paths, and ensuring the resolved path remains confined within the intended upload directory (UPLOAD_PATH). Additionally, enforce a whitelist of allowed file extensions, such as only permitting image files like .jpg or .png. Applying these input validation and restriction measures will prevent attackers from reading arbitrary files on the server. [1]