CVE-2025-56396: RuoYi · n/a
Affects RuoYiSource CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 26 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHuby_project/RuoYipkg:github/y_project/RuoYiOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Conduct an immediate audit of access control policies within Ruoyi installations, focusing on department-level permissions versus individual user rights. 2. Implement the principle of least privilege by ensuring users and departments have only the minimum necessary permissions. 3. Monitor logs and alerts for unusual privilege escalations or access patterns indicative of exploitation attempts. 4. Segment network access to limit lateral movement opportunities if escalation occurs. 5. Engage with Ruoyi vendors or community to obtain patches or updates as soon as they become available. 6. Consider deploying compensating controls such as multi-factor authentication and enhanced session monitoring for privileged accounts. 7. Educate IT and security teams about this vulnerability to ensure rapid response capability. 8. If possible, temporarily restrict or isolate systems running vulnerable versions until patches are applied. 9. Review and update incident response plans to include scenarios involving privilege escalation attacks. 10. Collaborate with cybersecurity information sharing groups to stay informed about emerging exploit techniques related to this vulnerability.
Description
An issue was discovered in Ruoyi 4.8.1 allowing attackers to gain escalated privileges due to the owning department having higher rights than the active user.