CVE-2026-105611 in SpringBlade
Summary
by MITRE • 10/06/2026
A vulnerability was determined in chillzhuang SpringBlade up to 5.0.1. This affects an unknown function of the file blade-service/blade-system/src/main/java/org/springblade/system/controller/RoleController.java of the component User Detail Endpoint. This manipulation of the argument ID causes improper authorization. The attack can be initiated remotely. The exploit has been publicly disclosed and may be utilized. The project was informed of the problem early through an issue report but has not responded yet.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Analysis
by VulDB Data Team • 10/06/2026
The identified vulnerability resides within the SpringBlade framework, specifically affecting versions up to 5.0.1, in a component designated as the User Detail Endpoint. This security flaw is located within the RoleController.java file under the blade-service/blade-system module. The core technical issue stems from improper authorization controls associated with an unknown function that processes argument inputs, particularly focusing on how the ID parameter is handled during request execution. Because the application fails to adequately verify whether the authenticated user has sufficient privileges to access or modify the resource identified by the provided ID, it creates a classic Insecure Direct Object Reference scenario. This type of flaw allows attackers to manipulate input parameters to bypass intended access restrictions and interact with data belonging to other users or administrative entities without proper permission checks.
From an operational perspective, this vulnerability enables remote exploitation, meaning that an attacker does not need physical or local network proximity to initiate the attack. By crafting specific HTTP requests with manipulated ID values, a malicious actor can potentially retrieve sensitive user details, modify role assignments, or perform other unauthorized actions within the system. The severity of this impact is compounded by the fact that the exploit has been publicly disclosed and is known to be functional in real-world scenarios. This public availability significantly increases the risk landscape, as automated scanning tools and opportunistic attackers can readily leverage existing proof-of-concept code to target vulnerable instances across the internet.
The project maintainers were notified of this issue through an official report but have not yet issued a response or provided a patch. In such situations where vendor remediation is delayed, organizations relying on SpringBlade must implement compensating controls to mitigate the risk. Immediate steps should include restricting access to the affected endpoints via web application firewalls by validating user roles against requested resource IDs at the network perimeter level. Additionally, implementing strict input validation and ensuring that all API endpoints enforce robust server-side authorization checks is critical. Until an official patch is released, continuous monitoring of system logs for anomalous access patterns related to role management functions can help detect potential exploitation attempts early.
This vulnerability aligns with Common Weakness Enumeration identifier CWE-284, which describes Improper Access Control, and specifically maps to the ATT&CK technique T1078, Valid Accounts, as it involves leveraging legitimate credentials to perform unauthorized actions due to flawed authorization logic. The lack of vendor response highlights the importance of maintaining up-to-date vulnerability intelligence and having incident response plans that account for unpatched third-party dependencies in critical infrastructure environments.