CVE-2026-38812
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 · uneditedRuoYi 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.
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 confidenceRuoYi v4.8.2 contains a SQL injection vulnerability in the code generation module at the /tool/gen/createTable endpoint. An authenticated attacker with administrative privileges can inject malicious SQL statements through this endpoint to exfiltrate sensitive database information, leading to complete database compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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.
-
Identify if RuoYi is installedSearch for RuoYi application files or check running web applications for RuoYi framework indicators such as common RuoYi web paths, class files with RuoYi package names, or application banners.Affected if RuoYi framework is present in the environment
-
Check the installed RuoYi versionLocate version information in the RuoYi application - typically found in pom.xml, version files, or the system info page if available. Compare the installed version to the affected range around v4.8.2.Affected if The installed version is 4.8.2 or falls within the affected version range
-
Verify the code generation module is presentCheck if the /tool/gen/ path exists in the deployed application. The vulnerability resides in the code generation functionality, so confirm whether this module has been deployed.Affected if The /tool/gen/createTable endpoint is accessible in the application
-
Check endpoint accessibility and authentication requirementsAttempt to access or probe the /tool/gen/createTable endpoint to determine if it requires authentication. Review web.xml or security configuration to confirm whether administrative privileges are enforced for this endpoint.Affected if The endpoint is accessible without proper admin authentication or authentication can be bypassed
-
Review database query implementation in the code generation moduleIf code access is available, inspect the controller handling /tool/gen/createTable for direct string concatenation in SQL queries. Look for evidence of unsanitized input being passed to database queries without parameterized queries or prepared statements.Affected if The code uses string concatenation or unsanitized input in SQL queries within the createTable functionality
A user is affected if RuoYi version 4.8.2 or an affected version is installed, the /tool/gen/createTable endpoint is accessible, and the code generation module uses unsanitized input in SQL queries.
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 dataUpgrade to a patched version of RuoYi. Apply input validation and use parameterized queries/prepared statements in the code generation module to prevent SQL injection. Apply least-privilege database accounts to limit impact of any successful injection.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-38812 — 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-2026-38812 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