CVE-2023-27025 — ruoyi
HIGHCVE-2023-27025 is a high-severity (CVSS 7.5) CWE-494 vulnerability in com.ruoyi:ruoyi. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for com.ruoyi:ruoyi — see the affected versions and patch details below.
RuoYi vulnerable to arbitrary file download
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-27025.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
com.ruoyi:ruoyiReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
An arbitrary file download vulnerability in the background management module of RuoYi v4.7.6 and below allows attackers to download arbitrary files in the server.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.ruoyi:ruoyi | all versions | 4.7.7com.ruoyi:ruoyi:4.7.7 |
Affected Products
ruoyiruoyiResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.ruoyi:ruoyi, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.ruoyi:ruoyi to 4.7.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-27025 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2023-27025 in your dependencies?
Find it across Maven, including transitive dependencies.