dbcve.org
Ruoyi GoApplication · Lostvip

CVE-2025-10218

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 2.1. This affects the function SelectListPage of the file modules/system/dao/SysRoleDao.go of the component Background Management Page. This manipulation of the argument sortName causes sql injection. Remote exploitation of the attack is possible. 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 2.1 allows remote attackers to inject malicious SQL via the sortName parameter in the SysRoleDao SelectListPage function used by the Background Management Page.

MitigationImplement parameterized queries and input validation/whitelisting for the sortName parameter in the SelectListPage function to prevent SQL injection.

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 and version
    Search for RuoYi Go application files or check deployed web application for version identifier. Common locations include application root directories, pom.xml or build.gradle files, or the application's footer/info page.
    Affected if The installed version is Lostvip Ruoyi Go version 2.1 exactly
  2. Locate SysRoleDao.java file
    Search the application source code or deployment for the file SysRoleDao.java, typically found in the DAO or mapper layer under paths like src/main/java/com/ruoyi/ or similar package structures.
    Affected if The SysRoleDao.java file exists in the application and contains the SelectListPage function
  3. Verify SelectListPage function implementation
    Open SysRoleDao.java and examine the SelectListPage method. Look for how the sortName parameter is used in the SQL query - whether it is directly concatenated into the SQL string or passed through a parameter binding mechanism.
    Affected if The sortName parameter is used directly in SQL string concatenation without proper parameterization or escaping
  4. Check Background Management Page accessibility
    Attempt to access the admin/management interface endpoint (commonly /admin, /system/role, or similar role management paths) to determine if the vulnerable endpoint is exposed.
    Affected if The Background Management Page with role management functionality is accessible and the vulnerable role list endpoint responds to requests
  5. Test sortName parameter for injection
    If you have access to the application, send a crafted request to the role list endpoint with a test payload in the sortName parameter, such as a time-based sleep command or error-inducing SQL syntax, observing for delayed responses or database errors.
    Affected if The application responds to SQL injection payloads in the sortName parameter, confirming the vulnerability is exploitable

A defender is affected if they are running Lostvip Ruoyi Go version 2.1 and the SysRoleDao SelectListPage function uses the sortName parameter in a direct SQL concatenation rather than parameterized queries.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement parameterized queries and input validation/whitelisting for the sortName parameter in the SelectListPage function to prevent SQL injection.

Fix this in Ruoyi Go Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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