dbcve.org
Ruoyi GoApplication · Lostvip

CVE-2025-9413

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 flaw has been found in lostvip-com ruoyi-go up to 2.1. This impacts the function SelectListByPage of the file modules/system/system_router.go. This manipulation of the argument orderByColumn/isAsc causes sql injection. The attack may be initiated remotely. The exploit has been published 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 confidence

SQL injection vulnerability in ruoyi-go up to v2.1 allows remote attackers to inject arbitrary SQL via the orderByColumn and isAsc parameters in the SelectListByPage function within modules/system/system_router.go. The lack of input sanitization on these pagination/sorting parameters enables attackers to manipulate SQL queries.

MitigationImplement strict input validation allowing only predefined column names and safe values for the orderByColumn and isAsc parameters, or refactor to use parameterized queries. If no patched version exists, apply compensating controls such as WAF rules or disable the affected endpoint until a fix is available.

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 RuoYi Go installation
    Locate the RuoYi Go application by searching for the binary, source code directory, or running service named 'ruoyi' or containing 'ruoyi-go' in its path. Check common deployment locations such as /opt/ruoyi-go, /home/ruoyi, or the application root directory where the go.mod file may exist.
    Affected if The application is not found or is a different product entirely.
  2. Verify affected version
    Check the installed version by examining the go.mod file for the version tag, or run 'go list -m all' if source is available, or use 'ruoyi-go --version' if the binary supports version flag. Compare against the affected range: <= 2.1.
    Affected if The version is 2.1 or lower, or if version cannot be determined but the code matches the vulnerable release.
  3. Locate vulnerable code file
    Find the file modules/system/system_router.go in the source code or deployment. Open the file and locate the SelectListByPage function. Examine how the orderByColumn and isAsc parameters are processed - look for direct string concatenation or lack of parameterized query usage.
    Affected if The file exists and contains the SelectListByPage function with orderByColumn/isAsc parameters being used in SQL queries without sanitization or parameterized binding.
  4. Confirm endpoint exposure
    Identify the HTTP route that triggers this function. Check the router configuration files to determine if the endpoint using SelectListByPage is exposed via HTTP. Look for route definitions that map to system router operations that include pagination parameters.
    Affected if The vulnerable endpoint is exposed over HTTP/HTTPS and accepts user-controlled orderByColumn and isAsc parameters without validation.

You are affected if RuoYi Go version 2.1 or lower is deployed, the vulnerable SelectListByPage function in system_router.go uses orderByColumn/isAsc parameters without input validation, and the corresponding endpoint is network-accessible.

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 strict input validation allowing only predefined column names and safe values for the orderByColumn and isAsc parameters, or refactor to use parameterized queries. If no patched version exists, apply compensating controls such as WAF rules or disable the affected endpoint until a fix is available.

Fix this in Ruoyi Go Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing10.0 h
  • Review / QA6.0 h
38.0 hours of engineering $6,660
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-9413 — 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-9413 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