CVE-2025-10473
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 · uneditedA security flaw has been discovered in yangzongzhuan RuoYi up to 4.8.1. This impacts the function filterKeyword of the file /com/ruoyi/common/utils/sql/SqlUtil.java of the component Blacklist Handler. The manipulation results in sql injection. The attack may be launched remotely. The exploit has been released to the public and may be exploited.
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 confidenceA SQL injection vulnerability exists in the filterKeyword function of SqlUtil.java in RuoYi framework up to version 4.8.1. The blacklist handler can be bypassed, allowing attackers to inject malicious SQL queries through user-controlled input processed by this function.
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.8.1CVSS 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 framework is deployedSearch for RuoYi-specific artifacts such as JAR files, WAR archives, or project directories containing 'ruoyi' in the filename. Check application classpath or dependencies for com.ruoyi package references.Affected if RuoYi framework components are present in the environment and the version is unknown or <= 4.8.1
-
Determine the installed RuoYi versionLocate the version file, build configuration (pom.xml), or manifest that declares the RuoYi version. Common locations include the root directory version file, application.properties with version properties, or the compiled WAR/MAR archive metadata.Affected if The version is 4.8.1 or below, or the version cannot be determined but RuoYi is present
-
Locate SqlUtil.java and inspect filterKeyword functionSearch the codebase for SqlUtil.java file. Examine the filterKeyword function to confirm it uses a blacklist-based approach for input sanitization rather than parameterized queries or whitelisting.Affected if SqlUtil.java exists with a filterKeyword function that relies solely on blacklist filtering for SQL injection prevention
-
Verify if user input reaches filterKeyword without parameterized queriesTrace the data flow from HTTP request parameters (query strings, form inputs, JSON body fields) through the application to the filterKeyword function call. Check if prepared statements or parameterized queries are used before or after the blacklist filter.Affected if User-supplied input flows directly to the filterKeyword blacklist handler without prior parameterized query binding, or the filter is the only SQL injection protection in that code path
The environment is affected if RuoYi framework version 4.8.1 or below is deployed and user-controlled input can reach the filterKeyword blacklist handler without parameterized query protection.
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 dataUpdate RuoYi to the latest patched version. If immediate patching is not possible, implement robust input validation and parameterized queries to neutralize SQL injection payloads before reaching the blacklist handler.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10473 — 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-2025-10473 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