CVE-2025-3202
Ageerle Ruoyi-ai privilege escalation
- Published4 Apr 2025
Description
A vulnerability classified as critical has been found in ageerle ruoyi-ai up to 2.0.0. Affected is an unknown function of the file ruoyi-modules/ruoyi-system/src/main/java/org/ruoyi/system/controller/system/SysNoticeController.java. The manipulation leads to improper authorization. It is possible to launch the attack 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 name of the patch is 6382e177bf90cc56ff70521842409e35c50df32d. 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/commit/6382e177bf90cc56ff70521842409e35c50df32d
- https://github.com/ageerle/ruoyi-ai/issues/44#issue-2957771318
- https://github.com/ageerle/ruoyi-ai/releases/tag/v2.0.1
- https://github.com/Tr0e/CVE_Hunter/blob/main/ruoyi-ai/ruoyi-ai_UnauthorizedAccess_02.md
- https://vuldb.com/?ctiid.303156
- https://vuldb.com/?id.303156
- https://vuldb.com/?submit.545866
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2025-3202 being actively exploited?
CVE-2025-3202 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.53%.
How severe is CVE-2025-3202?
CVE-2025-3202 has a CVSS 3.1 base score of 7.3, rated high. EPSS estimates a 0.53% probability of exploitation.
Which products are affected by CVE-2025-3202?
Affected products include Ageerle Ruoyi-ai.
How do I fix CVE-2025-3202?
Upgrade affected software to a fixed version, for example Ageerle Ruoyi-ai 2.0.1 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2025-3202 against the real software inventory on every managed device, as each hourly inventory arrives. 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.