# CVE-2025-11631: RainyGao DocSys deleteDoc.do path traversal

> Remote attackers can exploit a path traversal vulnerability in the deleteDoc.do endpoint to read or modify arbitrary files.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2025
- **Updated:** 17 Oct 2025
- **Also known as:** GHSA-jwwr-9265-56jg

## What is CVE-2025-11631?

CVE-2025-11631 is a medium-severity path traversal vulnerability in RainyGao DocSys, published on 12 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was determined in RainyGao DocSys up to 2.02.36. Affected by this vulnerability is an unknown functionality of the file /Doc/deleteDoc.do. Executing manipulation of the argument path can lead to path traversal. The attack can be launched remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2025-11631?

It affects 1 product.


Products: Docsys Project Docsys.

## How do I fix CVE-2025-11631?

No fix has been published for CVE-2025-11631 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-11631 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-11631 exists.

## Other vulnerabilities in RainyGao DocSys

- [CVE-2025-15492](https://insights.sbomify.com/CVE-2025-15492/): RainyGao DocSys GroupMemberMapper.xml sql injection (medium 5.3)
- [CVE-2025-15493](https://insights.sbomify.com/CVE-2025-15493/): RainyGao DocSys ReposAuthMapper.xml sql injection (medium 5.3)
- [CVE-2025-15494](https://insights.sbomify.com/CVE-2025-15494/): RainyGao DocSys UserMapper.xml sql injection (medium 5.3)
- [CVE-2025-11629](https://insights.sbomify.com/CVE-2025-11629/): RainyGao DocSys getUserList.do getUserList sql injection (medium 5.3)
- [CVE-2025-11630](https://insights.sbomify.com/CVE-2025-11630/): RainyGao DocSys File Upload uploadDoc.do updateRealDoc path traversal (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-11631 and fix it if it is affected.

What it is: CVE-2025-11631 is a medium-severity path traversal vulnerability in RainyGao DocSys, published on 12 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-11631 exists.

Affected product: RainyGao DocSys. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-11631/ (Markdown: https://insights.sbomify.com/CVE-2025-11631/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-11631
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-11631
- OSV: https://osv.dev/vulnerability/CVE-2025-11631

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-11631/
Summaries are generated and may contain mistakes; the official description above is the record.