dbcve.org
Ruoyi GoApplication · Lostvip

CVE-2025-9410

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-25
Fix available
A fix is available. Upgrade to after 2.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
A weakness has been identified in lostvip-com ruoyi-go up to 2.1. The affected element is the function SelectListByPage of the file modules/system/dao/GenTableDao.go. Executing manipulation of the argument isAsc/orderByColumn can lead to sql injection. It is possible to launch the attack remotely. The exploit has been made available to the public and could be exploited. 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 confidence

SQL injection vulnerability in the SelectListByPage function of GenTableDao.go in ruoyi-go up to v2.1. The orderByColumn and isAsc parameters are not properly sanitized before being used in SQL queries, allowing attackers to inject malicious SQL code through these pagination/sorting parameters.

MitigationImplement whitelist-based validation for orderByColumn values (allowing only known safe column names) and use prepared/parameterized queries for dynamic ORDER BY clauses, or migrate to an ORM that handles parameterization automatically.

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
Ruoyi GoApplication
Affected:<= 2.1

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if using ruoyi-go framework
    Check your project's dependencies (go.mod, vendor folder, or built binary) for 'ruoyi' or 'ruoyi-go' references, or inspect the application binary for version strings using 'strings <binary> | grep -i ruoyi'
    Affected if The application uses ruoyi-go framework and version is <= 2.1
  2. Locate GenTableDao.go in the codebase
    Search for file named 'GenTableDao.go' in the application source code, typically under a 'ruoyi' or 'RuoYi' directory structure
    Affected if The file GenTableDao.go exists in the codebase and contains the SelectListByPage function
  3. Inspect SelectListByPage function for unsanitized parameters
    Open GenTableDao.go and examine the SelectListByPage function; look for direct string concatenation or interpolation of orderByColumn and isAsc variables into SQL queries without using parameterized queries or whitelist validation
    Affected if The orderByColumn and isAsc parameters are concatenated directly into SQL without sanitization or prepared statement parameterization
  4. Check if pagination/sorting features are in use
    Review application logs or HTTP requests for endpoints that accept 'orderByColumn' and 'isAsc' parameters (commonly used in table pagination APIs)
    Affected if The application exposes endpoints accepting orderByColumn and isAsc parameters that flow to GenTableDao.go SelectListByPage function
  5. Verify Go version used
    Check the Go version in go.mod or used to build the application (go version command or in build logs)
    Affected if Running Go version is unpatched and application contains the vulnerable code path

The environment is affected if it uses ruoyi-go version 2.1 or earlier, contains the vulnerable GenTableDao.go with SelectListByPage function, and the application uses endpoints that pass orderByColumn or isAsc parameters without sanitization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 2.1
Interim mitigation

Implement whitelist-based validation for orderByColumn values (allowing only known safe column names) and use prepared/parameterized queries for dynamic ORDER BY clauses, or migrate to an ORM that handles parameterization automatically.

Fix this in Ruoyi Go Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-9410 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-9410 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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