CVE-2024-57521
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 · uneditedSQL Injection vulnerability in RuoYi v.4.7.9 and before allows a remote attacker to execute arbitrary code via the createTable function in SqlUtil.java.
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 · moderate confidenceSQL injection vulnerability in the createTable function of SqlUtil.java in RuoYi framework versions 4.7.9 and earlier allows remote attackers to execute arbitrary code through unsanitized SQL input.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 4.7.9CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 RuoYi framework installationSearch for RuoYi framework files or artifacts in your deployment. Look for jar files, war files, or project directories containing 'ruoyi' in the filename, or check application startup logs for RuoYi initialization messages.Affected if RuoYi framework is not present in your environment, you are not affected.
-
Check installed RuoYi versionLocate the version information for your RuoYi installation. Check pom.xml files, version.properties, or the application's build manifest. Compare your version against the affected range of 4.7.9 and earlier.Affected if Your installed RuoYi version is 4.7.9 or lower, proceed to next checks.
-
Locate SqlUtil.java in your codebaseSearch your deployed application files for SqlUtil.java. This file should contain the createTable function that is vulnerable to SQL injection.Affected if SqlUtil.java with createTable function exists in your deployment, the vulnerable code is present.
-
Determine if createTable function is web-accessibleReview your application's routing or controller configuration to determine if the createTable function in SqlUtil.java is exposed through a web API endpoint or service that accepts user requests.Affected if The createTable function is exposed via web interface or API, the vulnerability is reachable.
-
Check if table creation parameters accept user inputInspect how the createTable function is invoked. Determine whether any parameters used in table creation (such as table name, column definitions, or schema settings) can be controlled by external users through HTTP requests or API calls.Affected if User-controlled input can reach the createTable function without sanitization, you are affected by this SQL injection vulnerability.
You are affected if you have RuoYi version 4.7.9 or earlier with the SqlUtil.java createTable function exposed to user input without sanitization.
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; if no patch available, refactor the createTable function to use parameterized queries or prepared statements, and implement strict input validation on all table creation parameters.
- Consultation6.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,712.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-57521 — 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-2024-57521 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