dbcve.org
Ruoyi AiApplication · Ageerle

CVE-2025-6466

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-22
Fix available
A fix is available. Upgrade to 2.0.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

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 vulnerability was found in ageerle ruoyi-ai 2.0.0 and classified as critical. Affected by this issue is the function speechToTextTranscriptionsV2/upload of the file ruoyi-modules/ruoyi-system/src/main/java/org/ruoyi/system/service/impl/SseServiceImpl.java. The manipulation of the argument File leads to unrestricted upload. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 2.0.1 is able to address this issue. The patch is identified as 4e93ac86d4891c59ecfcd27c051de9b3c5379315. It is recommended to upgrade the affected component.

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

This is an unrestricted file upload vulnerability in the ruoyi-ai system's speech-to-text transcription upload function (speechToTextTranscriptionsV2/upload). The lack of proper file validation in SseServiceImpl.java allows attackers to upload arbitrary files to the server, potentially achieving remote code execution. The critical CVSS score of 9.8 reflects the network-exploitable, low-complexity nature requiring no authentication.

MitigationUpgrade the affected component from version 2.0.0 to version 2.0.1, which contains the patch commit 4e93ac86d4891c59ecfcd27c051de9b3c5379315. Prior to upgrade, review server logs for signs of exploitation since this vulnerability is publicly known.

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 AiApplication
Affected:< 2.0.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 AI deployment
    Search for RuoYi AI application files, typically deployed as a Java web application. Look for the characteristic directory structure containing 'ruoyi' or 'ruoyi-ai' in the application path.
    Affected if RuoYi AI system is present in the environment
  2. Check installed version
    Locate the version manifest or build files (pom.xml, application.yml, or version.properties) within the RuoYi AI deployment directory and compare the version number to 2.0.1.
    Affected if Installed version is below 2.0.1
  3. Verify speech-to-text upload endpoint exists
    Inspect the deployed SseServiceImpl.java file or its compiled class file within the application. Confirm that the speechToTextTranscriptionsV2/upload method is present and accessible.
    Affected if The upload endpoint exists in the deployment
  4. Inspect upload directory for suspicious files
    Check common upload directories (typically /upload, /uploads, or /temp within the web root) for unexpected executable files such as .jsp, .php, .jar, .exe, or shell scripts that were not intentionally uploaded.
    Affected if Unexpected executable files are found in upload directories
  5. Review access logs for upload endpoint probing
    Search HTTP access logs for requests to paths containing 'speechToTextTranscriptionsV2/upload' or similar variations, especially with unusual file extensions or multiple POST requests from external IPs.
    Affected if Log entries show suspicious requests to the upload endpoint

The environment is affected if RuoYi AI version is below 2.0.1 and the speech-to-text upload endpoint is exposed.

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.

dbcve · scoped
Upgrade available Upgrade to 2.0.1 or later
Fixed in 2.0.1
Vendor patch github.com →
Interim mitigation

Upgrade the affected component from version 2.0.0 to version 2.0.1, which contains the patch commit 4e93ac86d4891c59ecfcd27c051de9b3c5379315. Prior to upgrade, review server logs for signs of exploitation since this vulnerability is publicly known.

Recommended fix High confidence

2.0.1

  1. 1. Ensure you have a complete backup of your current Ruoyi Ai installation and database.
  2. 2. Stop the running Ruoyi Ai application services.
  3. 3. Update your project dependencies or pull the latest version of the ruoyi-ai code from the repository.
  4. 4. Ensure you upgrade to version 2.0.1 or later which contains the fix for the unrestricted file upload vulnerability in the speechToTextTranscriptionsV2/upload function.
  5. 5. Rebuild the application with the new version.
  6. 6. Start the application and verify the service is running correctly.
  7. 7. Test that the file upload functionality in SseServiceImpl.java now properly validates uploaded files.
Caveat Review release notes for 2.0.1 to check for any breaking changes or deprecations before upgrading in production

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ruoyi Ai Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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