Authenticated arbitrary file upload via unchecked path
Published Oct 12, 2025 · Updated Oct 12, 2025
Path traversal in RainyGao DocSys 2.02.0 through 2.02.36 allows remote authenticated users to write files outside the upload directory. /Doc/uploadDoc.do passes the path and name fields through buildBasicDoc and addDoc to updateRealDoc, which calls FileUtil.saveFile without validation. Low-privilege application access is required, and successful exploitation writes an attacker-chosen file to a filesystem location such as the server root.
Summary
What happened
Path traversal in RainyGao DocSys 2.02.0 through 2.02.36 allows remote authenticated users to write files outside the upload directory. /Doc/uploadDoc.do passes the path and name fields through buildBasicDoc and addDoc to updateRealDoc, which calls FileUtil.saveFile without validation. Low-privilege application access is required, and successful exploitation writes an attacker-chosen file to a filesystem location such as the server root.
The record
- CVE
- CVE-2025-11630
- Published
- Oct 12, 2025
- Updated
- Oct 12, 2025
- Vendor
- RainyGao
- Product
- DocSys
- Classifications
- CWE-22, T1105
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 12, 2025CVE publishedPublication date reported by the CVE source.
- Oct 12, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.02.0
- Affected versionversion=2.02.1
- Affected versionversion=2.02.10
- Affected versionversion=2.02.11
- Affected versionversion=2.02.12
- Affected versionversion=2.02.13
- Affected versionversion=2.02.14
- Affected versionversion=2.02.15
- Affected versionversion=2.02.16
- Affected versionversion=2.02.17
- Affected versionversion=2.02.18
- Affected versionversion=2.02.19
- Affected versionversion=2.02.2
- Affected versionversion=2.02.20
- Affected versionversion=2.02.21
- Affected versionversion=2.02.22
- Affected versionversion=2.02.23
- Affected versionversion=2.02.24
- Affected versionversion=2.02.25
- Affected versionversion=2.02.26
- Affected versionversion=2.02.27
- Affected versionversion=2.02.28
- Affected versionversion=2.02.29
- Affected versionversion=2.02.3
- Affected versionversion=2.02.30
- Affected versionversion=2.02.31
- Affected versionversion=2.02.32
- Affected versionversion=2.02.33
- Affected versionversion=2.02.34
- Affected versionversion=2.02.35
- Affected versionversion=2.02.36
- Affected versionversion=2.02.4
- Affected versionversion=2.02.5
- Affected versionversion=2.02.6
- Affected versionversion=2.02.7
- Affected versionversion=2.02.8
- Affected versionversion=2.02.9
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- DocSys arbitrary file upload proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo