# CVE-2022-4416: RainyGao DocSys getReposAllUsers.do getReposAllUsers sql injection

> Remote attackers can exploit SQL injection in RainyGao DocSys to read or modify database contents via the getReposAllUsers endpoint.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **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 Dec 2022
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-rcmh-jmm5-hqq7

## What is CVE-2022-4416?

CVE-2022-4416 is a medium-severity SQL injection vulnerability in RainyGao DocSys, published on 12 Dec 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in RainyGao DocSys. It has been declared as critical. This vulnerability affects the function getReposAllUsers of the file /DocSystem/Repos/getReposAllUsers.do. The manipulation of the argument searchWord/reposId leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. VDB-215278 is the identifier assigned to this vulnerability.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-707 (Improper Neutralization)

## Which versions are affected by CVE-2022-4416?

It affects 1 product.


Products: Mxsdoc Project Mxsdoc.

## How do I fix CVE-2022-4416?

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

## Is CVE-2022-4416 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-4416 and fix it if it is affected.

What it is: CVE-2022-4416 is a medium-severity SQL injection vulnerability in RainyGao DocSys, published on 12 Dec 2022. 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-2022-4416 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-2022-4416/ (Markdown: https://insights.sbomify.com/CVE-2022-4416/index.md)
```

## Sources

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

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