CVE-2025-11630
BaseFortify
Publication date: 2025-10-12
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 |
|---|---|---|
| docsys_project | docsys | to 2.02.36 (inc) |
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-11630 is a path traversal vulnerability in RainyGao DocSys up to version 2.02.36, specifically in the updateRealDoc function of the /Doc/uploadDoc.do file upload component. It occurs because the 'path' argument is not properly sanitized, allowing an attacker to manipulate it to traverse directories outside the intended folder. This enables unauthorized file uploads to arbitrary locations on the server, potentially leading to remote code execution or server compromise. [2, 3]
How can this vulnerability impact me? :
This vulnerability can allow an attacker to upload malicious files to unintended locations on the server remotely without authentication. This can lead to unauthorized access, remote code execution, compromise of system confidentiality, integrity, and availability, and potentially full server takeover. [2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring attempts to exploit the path traversal in the /Doc/uploadDoc.do interface, specifically targeting the updateRealDoc function with manipulated 'path' arguments. Since a proof-of-concept exploit is publicly available on GitHub, you can look for suspicious HTTP POST requests to /Doc/uploadDoc.do containing path traversal patterns such as '../' sequences in the 'path' parameter. Network intrusion detection systems (NIDS) or web application firewalls (WAF) can be configured to alert on such patterns. Additionally, you can use curl or similar tools to test the endpoint manually, for example: curl -X POST -F "path=../../../../etc/passwd" http://target/Doc/uploadDoc.do. Monitoring server logs for unusual file uploads or access outside expected directories can also help detect exploitation attempts. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include disabling or restricting access to the /Doc/uploadDoc.do endpoint to prevent exploitation. Since no patches or vendor responses are available, it is recommended to replace the affected product or upgrade to a version without this vulnerability if available. Implementing strict input validation and sanitization on the 'path' parameter to prevent path traversal is critical. Additionally, deploying web application firewalls (WAF) to block malicious payloads targeting this vulnerability and monitoring for suspicious activity can reduce risk. Limiting privileges of the application user to restrict file system access can also help mitigate impact. [3]