CVE-2025-11630
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 was found in RainyGao DocSys up to 2.02.36. Affected is the function updateRealDoc of the file /Doc/uploadDoc.do of the component File Upload. Performing manipulation of the argument path results in path traversal. The attack can be initiated remotely. The exploit has been made public and could 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 confidenceA path traversal vulnerability exists in RainyGao DocSys up to version 2.02.36 within the file upload functionality at /Doc/uploadDoc.do. The updateRealDoc function fails to properly validate the 'path' argument, allowing attackers to manipulate file upload paths using directory traversal sequences (e.g., ../../../') to write files to arbitrary locations on the server. This remote, unauthenticated vulnerability carries a CVSS 9.8 critical rating due to the potential for complete system 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 RainyGao DocSys (Project Docsys) is installed in your environment. Check for the application directory, web accessible paths containing 'DocSys' or 'Docsys', or look for the /Doc/uploadDoc.do endpoint in your web server logs or directory structure.Affected if The application is installed and accessible on the network
-
Check installed versionLocate version information for your Docsys installation. Check application configuration files, about pages, or the application itself for the version number. Common locations may include config files in the DocSys directory or version info displayed in the application UI.Affected if The installed version is 2.02.36 or lower (any version up to and including 2.02.36)
-
Verify uploadDoc.do is accessibleTest if the /Doc/uploadDoc.do endpoint is reachable via HTTP/HTTPS. Attempt to access this endpoint directly in a browser or via curl to confirm the file upload component is exposed.Affected if The uploadDoc.do endpoint responds and accepts requests (even if authentication is required, the endpoint exists)
-
Check if path parameter accepts traversal sequencesInspect the application's behavior when submitting a file upload request with a manipulated 'path' parameter containing ../ sequences. Observe whether the application allows writing files outside the intended upload directory.Affected if The application allows path traversal in the 'path' parameter and writes files to directories outside the intended upload folder
You are affected if RainyGao DocSys (Project Docsys) version 2.02.36 or lower is installed and the /Doc/uploadDoc.do endpoint is accessible, as the path traversal vulnerability allows writing files to arbitrary directories.
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 dataImplement strict input validation and path sanitization on the path parameter using allowlists, normalize paths to prevent traversal sequences, restrict upload directories to a non-executable location, and consider adding authentication/authorization checks to the upload endpoint. Monitor for indicators of active exploitation given the public exploit availability.
- Consultation6.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,136.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11630 — 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-11630 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