CVE-2025-15494: RainyGao DocSys · SQL Injection
Affects RainyGao DocSysSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 9 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| RainyGaoDocSys | Affected
| Fixed in– |
GitHubrainygao/DocSyspkg:github/rainygao/DocSysOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Immediately restrict network access to the DocSys application, limiting it to trusted internal IP addresses and VPN users only. 2. Implement Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting the Username parameter. 3. Conduct thorough logging and monitoring of database queries and application logs to identify anomalous or suspicious activities indicative of SQL injection attempts. 4. Employ input validation and sanitization at the application layer if possible, even as a temporary measure, to filter out malicious input. 5. Isolate the DocSys database with strict access controls and least privilege principles to minimize damage if exploitation occurs. 6. Prepare for incident response by backing up critical data regularly and verifying backup integrity. 7. Engage with the vendor for updates and patches, and apply any official fixes immediately upon release. 8. Consider deploying database activity monitoring tools to detect unauthorized queries in real time. 9. Educate internal teams about the vulnerability and ensure rapid reporting of suspicious behavior related to DocSys. 10. If feasible, evaluate alternative document management solutions with stronger security postures until this vulnerability is resolved.
Description
A vulnerability has been found in RainyGao DocSys up to 2.02.37. This affects an unknown function of the file com/DocSystem/mapping/UserMapper.xml. The manipulation of the argument Username leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.