CVE-2025-11630

6.3 MEDIUM

📋 TL;DR

This CVE describes a path traversal vulnerability in RainyGao DocSys up to version 2.02.36. Attackers can remotely exploit the file upload function to write arbitrary files to unintended directories, potentially leading to unauthorized file access or system compromise. Organizations using vulnerable versions of DocSys are affected.

💻 Affected Systems

Products:
  • RainyGao DocSys
Versions: Up to and including 2.02.36
Operating Systems: Any OS running DocSys
Default Config Vulnerable: ⚠️ Yes
Notes: All installations with the vulnerable upload endpoint accessible are affected. No special configuration required.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Remote attackers could write malicious files to sensitive system directories, potentially achieving remote code execution, data theft, or complete system compromise.

🟠

Likely Case

Attackers upload malicious files to web-accessible directories, enabling web shell deployment, data exfiltration, or privilege escalation.

🟢

If Mitigated

With proper file upload validation and directory restrictions, impact is limited to unauthorized file writes within controlled directories.

🌐 Internet-Facing: HIGH - The vulnerability is remotely exploitable and public exploit details exist, making internet-facing instances prime targets.
🏢 Internal Only: MEDIUM - Internal attackers could exploit this for lateral movement or privilege escalation within the network.

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploit details are publicly available in GitHub repositories. The vulnerability requires manipulation of the 'path' parameter during file upload.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: None - vendor did not respond to disclosure

Restart Required: No

Instructions:

No official patch available. Consider upgrading to any version above 2.02.36 if available, or implement workarounds.

🔧 Temporary Workarounds

Web Application Firewall (WAF) Rules

all

Implement WAF rules to block path traversal patterns in file upload requests

Configure WAF to block requests containing '../', '..\', or similar traversal sequences in upload parameters

File Upload Restriction

all

Restrict file upload functionality to authenticated users only and implement strict file type validation

Implement authentication middleware for /Doc/uploadDoc.do endpoint
Configure file type whitelisting (e.g., only allow .doc, .pdf, .txt)

🧯 If You Can't Patch

  • Isolate DocSys instance behind network segmentation with strict inbound/outbound rules
  • Implement file integrity monitoring on web directories to detect unauthorized file writes

🔍 How to Verify

Check if Vulnerable:

Test if you can upload a file with path traversal sequences (e.g., '../../malicious.php') to /Doc/uploadDoc.do endpoint

Check Version:

Check DocSys version in web interface or configuration files

Verify Fix Applied:

Attempt the same path traversal upload test; successful blocking indicates mitigation

📡 Detection & Monitoring

Log Indicators:

  • Multiple failed upload attempts with path traversal patterns
  • Successful uploads to non-standard directories
  • Unusual file types in upload logs

Network Indicators:

  • HTTP POST requests to /Doc/uploadDoc.do containing '../' sequences
  • Unusual outbound connections from DocSys server

SIEM Query:

source="DocSys" AND (url_path="/Doc/uploadDoc.do" AND (request_body CONTAINS "../" OR request_body CONTAINS "..\"))

🔗 References

📤 Share & Export