CVE-2025-3199
Pandarobot Ruoyi Ai privilege escalation
- Published4 Apr 2025
Description
A vulnerability was found in ageerle ruoyi-ai up to 2.0.1 and classified as critical. Affected by this issue is some unknown functionality of the file ruoyi-modules/ruoyi-system/src/main/java/org/ruoyi/system/controller/system/SysModelController.java of the component API Interface. The manipulation leads to improper authorization. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 2.0.2 is able to address this issue. The name of the patch is c0daf641fb25b244591b7a6c3affa35c69d321fe. It is recommended to upgrade the affected component.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:LAffected products
Remediation
References
- https://github.com/ageerle/ruoyi-ai/issues/43
- https://github.com/ageerle/ruoyi-ai/issues/43#issuecomment-2763091490
- https://github.com/ageerle/ruoyi-ai/releases/tag/v2.0.2
- https://github.com/gwozai/ruoyi-ai/commit/c0daf641fb25b244591b7a6c3affa35c69d321fe
- https://github.com/Tr0e/CVE_Hunter/blob/main/ruoyi-ai/ruoyi-ai_UnauthorizedAccess_01.md
- https://vuldb.com/?ctiid.303152
- https://vuldb.com/?id.303152
- https://vuldb.com/?submit.545830
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2025-3199 being actively exploited?
CVE-2025-3199 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.63%.
How severe is CVE-2025-3199?
CVE-2025-3199 has a CVSS 3.1 base score of 7.3, rated high. EPSS estimates a 0.63% probability of exploitation.
Which products are affected by CVE-2025-3199?
Affected products include Pandarobot Ruoyi Ai.
How do I fix CVE-2025-3199?
Upgrade affected software to a fixed version, for example Pandarobot Ruoyi Ai 2.0.2 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2025-3199 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.