# CVE-2026-105158: RainyGao DocSys Database Management BaseController.java BaseController.createDBForMysql sql injection

> Remote attackers can exploit SQL injection in DocSys Database Management to read or modify database contents.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Oct 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-29mr-m6g4-8wq4

## What is CVE-2026-105158?

CVE-2026-105158 is a medium-severity SQL injection vulnerability in RainyGao DocSys, published on 4 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was detected in RainyGao DocSys up to 2.02.85. The impacted element is the function BaseController.createDBForMysql of the file BaseController.java of the component Database Management. The manipulation of the argument url results in sql injection. The attack can be executed remotely. The exploit is now public and may be used. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2026-105158?


## How do I fix CVE-2026-105158?

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

## Is CVE-2026-105158 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-105158 and fix it if it is affected.

What it is: CVE-2026-105158 is a medium-severity SQL injection vulnerability in RainyGao DocSys, published on 4 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-105158 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-2026-105158/ (Markdown: https://insights.sbomify.com/CVE-2026-105158/index.md)
```

## Sources

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

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