# CVE-2026-38812: SQL injection in n/a

> An authenticated administrator can exploit SQL injection in the code generation module to access sensitive database information.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jun 2026
- **Updated:** 16 Jun 2026
- **Also known as:** GHSA-x5vx-6h7v-vj45

## What is CVE-2026-38812?

CVE-2026-38812 is a critical SQL injection vulnerability in n/a, published on 15 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

RuoYi v4.8.2 is vulnerable to SQL Injection via the /tool/gen/createTable endpoint. The issue affects the code generation module and may allow an authenticated attacker with administrative privileges to access sensitive database information.

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

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


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

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

## Is CVE-2026-38812 being exploited?

There is no known exploitation of CVE-2026-38812 in the wild and no public exploit code.

Public exploit code:

- CVE-2026-38812 RuoYi v4.8.2 SQL Injection (github_poc): https://github.com/jjcjgo/CVE-2026-38812-RuoYi-SQL-Injection
- https://github.com/YYF1337/RuoYi-CVE-2026-38812-UNFIX (github_poc): https://github.com/YYF1337/RuoYi-CVE-2026-38812-UNFIX

## Fix prompt for AI coding agents

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

What it is: CVE-2026-38812 is a critical SQL injection vulnerability in n/a, published on 15 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-38812 in the wild and no public exploit code.

Affected product: n/a. 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-38812/ (Markdown: https://insights.sbomify.com/CVE-2026-38812/index.md)
```

## Sources

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

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