CVE-2025-11629
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSQL injection vulnerability in the getUserList function of /Manage/getUserList.do in RainyGao DocSys up to v2.02.36 allows remote attackers to inject malicious SQL queries via unsanitized input parameters, potentially enabling unauthorized data access, data exfiltration, or complete database compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2.02.36CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm RainyGao DocSys installationIdentify if the RainyGao DocSys application is present in your environment by checking for the application's web root directory, service running on typical ports (often 8080 or 8443), or by accessing the application's login page.Affected if The application is installed and accessible
-
Determine installed DocSys versionCheck the version of DocSys by accessing the admin interface, reviewing version files in the installation directory, or querying the application's /about or /version endpoint if available.Affected if The installed version is 2.02.36 or lower
-
Verify getUserList endpoint existsAttempt to access the /Manage/getUserList.do endpoint via HTTP/HTTPS request to confirm it is exposed in the environment.Affected if The endpoint responds (even with an error) indicating it exists and is reachable
-
Check for input validation on the endpointInspect application logs, WAF configurations, or reverse proxy settings to determine if any input sanitization or SQLi protection is present for the getUserList.do endpoint.Affected if No input validation or SQL injection protection is detected for this endpoint
If DocSys version 2.02.36 or lower is installed, the /Manage/getUserList.do endpoint is accessible, and no input validation exists on that endpoint, the environment is affected by CVE-2025-11629.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataSince the vendor did not respond, implement immediate compensating controls: add input validation/sanitization to the getUserList endpoint, deploy a WAF rule for SQLi detection, and consider disabling the affected functionality until a patched version is available; otherwise upgrade if a newer version is released.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11629 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-11629 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data