Skip to main content
VulnerabilityPublished Updated

CVE-2025-11629: RainyGao DocSys · SQL Injection

Affects RainyGao DocSysSource CVE Database V5

0

Public exploit available · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 10:12 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 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:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: evidence found.

    CVSS exploit maturity: proof of concept public

  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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
RainyGao DocSysAffected
  • 2.02.0 – 2.02.36
37 affected builds
Fixed in–

AI-suggested

  1. Immediately audit all RainyGao DocSys instances to identify affected versions (up to 2.02.36).
  2. Implement input validation and sanitization for the getUserList function, replacing vulnerable SQL queries with parameterized queries or prepared statements to prevent injection.
  3. If source code modification is not feasible, deploy web application firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting /Manage/getUserList.do.
  4. Restrict network access to the DocSys management interface, limiting exposure to trusted internal networks or VPNs.
  5. Monitor logs for suspicious query patterns or repeated access attempts to the vulnerable endpoint.
  6. Establish compensating controls such as database user privilege restrictions to minimize damage from potential exploitation.
  7. Engage with the vendor for updates or patches and subscribe to threat intelligence feeds for emerging exploit information.
  8. Conduct penetration testing focused on SQL injection vectors to verify mitigation effectiveness.
  9. Educate IT and security teams about this vulnerability and response procedures.
  10. Plan for eventual upgrade or replacement of the affected software if vendor support remains absent.

Description

A vulnerability has been found in RainyGao DocSys up to 2.02.36. This impacts the function getUserList of the file /Manage/getUserList.do. Such manipulation leads to sql injection. It is possible to launch the attack 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.

References

Community reviews

Loading reviews…