CVE-2025-9412
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 vulnerability was detected in lostvip-com ruoyi-go up to 2.1. This affects the function SelectListByPage of the file modules/system/dao/DictDataDao.go. The manipulation of the argument orderByColumn/isAsc results in sql injection. The attack can be launched remotely. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceSQL injection vulnerability in ruoyi-go up to v2.1 allows remote attackers to inject malicious SQL via the orderByColumn and isAsc parameters in the SelectListByPage function within DictDataDao.go. The application directly concatenates user-controlled input into SQL queries without proper parameterization or input validation.
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<= 2.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 the ruoyi-go version in useCheck your application's version file, build artifacts, or go.mod for the ruoyi-go dependency version (such as in a go.mod file or vendor directory)Affected if The version is 2.1 or any version lower than 2.1 (for example, 2.0, 1.x)
-
Locate DictDataDao.go in the codebaseSearch for the file DictDataDao.go in your project source code, typically found under a dao or repository directoryAffected if The file exists and contains the SelectListByPage function with SQL query logic
-
Inspect SelectListByPage for direct SQL concatenationOpen DictDataDao.go and locate the SelectListByPage function. Examine how the orderByColumn and isAsc parameters are used in the SQL query stringAffected if The code directly concatenates orderByColumn or isAsc into the SQL string without using parameterized queries or strict allowlist validation
-
Check if user input reaches the vulnerable functionTrace the code flow from HTTP handlers/controllers to the DictDataDao.SelectListByPage call to confirm that orderByColumn and isAsc are received from user requests (such as query parameters)Affected if The function accepts these parameters from untrusted user input (HTTP request parameters)
-
Verify lack of input validation on orderByColumn and isAscSearch for any validation logic that restricts orderByColumn to an allowlist of permitted column names, or that restricts isAsc to only 'ASC' or 'DESC' valuesAffected if No such validation exists, or the validation can be bypassed
You are affected if you are running Lostvip Ruoyi Go version 2.1 or lower and your application exposes the DictDataDao.SelectListByPage functionality with user-controlled orderByColumn or isAsc parameters.
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 dataImplement parameterized queries (prepared statements) for ORDER BY clauses, or validate orderByColumn against an allowlist of permitted column names, and strictly validate isAsc to only accept 'ASC' or 'DESC' values.
- Consultation4.0 h
- Implementation8.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9412 — 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-9412 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