Skip to main content
VulnerabilityPublished Updated

CVE-2025-15493: RainyGao DocSys · SQL Injection

Affects RainyGao DocSysSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 37% 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:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
RainyGaoDocSysAffected
  • =2.02.0
  • =2.02.1
  • =2.02.2
  • =2.02.3
  • =2.02.4
  • =2.02.5
  • =2.02.6
  • =2.02.7
  • =2.02.8
  • =2.02.9
  • =2.02.10
  • =2.02.11
  • =2.02.12
  • =2.02.13
  • =2.02.14
  • =2.02.15
  • =2.02.16
  • =2.02.17
  • =2.02.18
  • =2.02.19
  • =2.02.20
  • =2.02.21
  • =2.02.22
  • =2.02.23
  • =2.02.24
  • =2.02.25
  • =2.02.26
  • =2.02.27
  • =2.02.28
  • =2.02.29
  • =2.02.30
  • =2.02.31
  • =2.02.32
  • =2.02.33
  • =2.02.34
  • =2.02.35
  • =2.02.36
Fixed in–
GitHubrainygao/DocSyspkg:github/rainygao/DocSysOther threatsAffected
  • =2.02.0
  • =2.02.1
  • =2.02.2
  • =2.02.3
  • =2.02.4
  • =2.02.5
  • =2.02.6
  • =2.02.7
  • =2.02.8
  • =2.02.9
  • =2.02.10
  • =2.02.11
  • =2.02.12
  • =2.02.13
  • =2.02.14
  • =2.02.15
  • =2.02.16
  • =2.02.17
  • =2.02.18
  • =2.02.19
  • =2.02.20
  • =2.02.21
  • =2.02.22
  • =2.02.23
  • =2.02.24
  • =2.02.25
  • =2.02.26
  • =2.02.27
  • =2.02.28
  • =2.02.29
  • =2.02.30
  • =2.02.31
  • =2.02.32
  • =2.02.33
  • =2.02.34
  • =2.02.35
  • =2.02.36
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Given the absence of an official patch, organizations should implement the following specific mitigations: 1) Restrict network access to DocSys instances by enforcing strict firewall rules and limiting exposure to trusted internal networks only. 2) Employ Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting the searchWord parameter. 3) Conduct thorough input validation and sanitization at the application or proxy level if possible, especially for parameters interacting with database queries. 4) Monitor logs for suspicious query patterns or repeated failed attempts indicative of injection attempts. 5) Consider deploying database activity monitoring to detect anomalous SQL commands. 6) Plan for migration or replacement of DocSys if vendor support remains unavailable. 7) Isolate DocSys environments to minimize lateral movement in case of compromise. 8) Educate security teams about this vulnerability and ensure incident response plans include this threat scenario.

Description

A flaw has been found in RainyGao DocSys up to 2.02.36. The impacted element is an unknown function of the file src/com/DocSystem/mapping/ReposAuthMapper.xml. Executing a manipulation of the argument searchWord can lead to sql injection. It is possible to launch the attack remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

References

Community reviews

Loading reviews…