Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-46175: n/a

0
High
VulnerabilityCVE-2025-46175cvecve-2025-46175
Published: Wed Nov 26 2025 (11/26/2025, 00:00:00 UTC)
Source: CVE Database V5

Description

Ruoyi v4.8.0 is vulnerable to Incorrect Access Control. There is a missing checkUserDataScope permission check in the authRole method of SysUserController.java.

AI-Powered Analysis

AILast updated: 12/04/2025, 16:48:28 UTC

Technical Analysis

CVE-2025-46175 identifies an Incorrect Access Control vulnerability in Ruoyi version 4.8.0, specifically within the authRole method of the SysUserController.java component. The root cause is the absence of a critical permission check — checkUserDataScope — which is intended to restrict access based on user data scope permissions. Without this check, remote attackers can invoke the authRole method without authentication or user interaction, thereby bypassing intended access controls. This can lead to unauthorized disclosure of sensitive information, as the vulnerability impacts confidentiality but not integrity or availability. The CVSS 3.1 base score of 7.5 reflects the vulnerability’s network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), unchanged scope (S:U), and high confidentiality impact (C:H). Although no public exploits are currently known, the vulnerability’s characteristics make it a prime candidate for exploitation once weaponized. The CWE-284 classification confirms this is an access control weakness. The lack of patch links suggests that either patches are pending or not publicly disclosed yet, emphasizing the need for proactive mitigation. Organizations using Ruoyi or similar Java-based frameworks should audit their access control implementations, particularly around user role and permission checks, to prevent unauthorized data access.

Potential Impact

For European organizations, the primary impact of CVE-2025-46175 is unauthorized access to sensitive user data due to missing access control checks. This can lead to data breaches, regulatory non-compliance (e.g., GDPR violations), reputational damage, and potential financial penalties. Since the vulnerability does not affect integrity or availability, the main concern is confidentiality loss. Sectors such as finance, healthcare, government, and critical infrastructure that rely on Ruoyi or similar frameworks for user management are particularly at risk. The ease of exploitation without authentication or user interaction increases the threat level, potentially allowing attackers to harvest sensitive information remotely. This could facilitate further attacks such as identity theft, fraud, or targeted phishing campaigns. The absence of known exploits currently provides a window for mitigation before widespread exploitation occurs. However, the high CVSS score and nature of the vulnerability necessitate urgent attention to prevent exploitation in European environments.

Mitigation Recommendations

1. Immediately audit the authRole method and all related access control mechanisms in Ruoyi v4.8.0 to verify the presence of checkUserDataScope or equivalent permission checks. 2. If no official patch is available, implement custom access control validations to enforce user data scope restrictions before processing role authorization requests. 3. Restrict network access to the SysUserController endpoints to trusted internal networks or VPNs to reduce exposure. 4. Employ Web Application Firewalls (WAFs) with rules designed to detect and block anomalous requests targeting role authorization endpoints. 5. Monitor logs for unusual access patterns or unauthorized attempts to invoke authRole or related methods. 6. Engage with Ruoyi maintainers or vendors for timely patches and updates. 7. Conduct penetration testing focused on access control bypass scenarios to validate remediation effectiveness. 8. Educate development teams on secure coding practices related to access control and permission checks to prevent similar issues in future releases.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
mitre
Date Reserved
2025-04-22T00:00:00.000Z
Cvss Version
null
State
PUBLISHED

Threat ID: 6927289df2ee3b97400f2f22

Added to database: 11/26/2025, 4:19:41 PM

Last enriched: 12/4/2025, 4:48:28 PM

Last updated: 12/4/2025, 10:05:29 PM

Views: 33

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats