CVE-2026-108615 in JeecgBoot
Summary
by MITRE • 10/11/2026
JeecgBoot through 3.9.5 contains a missing authorization vulnerability in the AiragExtDataController delete handler that allows low-privileged authenticated users to delete AI evaluator records. Attackers can send DELETE requests to /airag/extData/delete with any id parameter to remove other users' AI evaluator or test-tracking records without owner or tenant checks.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Analysis
by VulDB Data Team • 10/11/2026
The vulnerability identified in JeecgBoot versions up to 3.9.5 represents a critical failure in access control mechanisms, specifically classified under CWE-862 as Missing Authorization. This flaw resides within the AiragExtDataController component, which is responsible for managing external data related to AI evaluators and test tracking systems. The core technical deficiency lies in the delete handler method, which processes HTTP DELETE requests directed at the /airag/extData/delete endpoint without performing adequate verification of user privileges or resource ownership. In a secure implementation, any operation that modifies persistent state must validate that the authenticated actor possesses explicit permission to act upon the specific target resource identified by the provided identifier.
When an attacker sends a DELETE request with an arbitrary id parameter, the application fails to check whether the requesting user is the owner of the record or belongs to the same tenant as the data being deleted. This lack of object-level authorization control allows low-privileged authenticated users to bypass intended security boundaries and remove records belonging to other users within the system. The vulnerability exploits the assumption that authentication alone provides sufficient context for action, ignoring the necessity of explicit authorization checks against specific resource attributes such as user_id or tenant_id fields associated with the database record.
The operational impact of this vulnerability is significant, particularly in multi-tenant environments where data isolation is paramount. By deleting AI evaluator records and test-tracking logs, an attacker can disrupt ongoing assessments, corrupt audit trails, and potentially cause denial of service for legitimate users who rely on these metrics for decision-making processes. Furthermore, the destruction of historical evaluation data may hinder compliance efforts that require retention of such information for regulatory auditing purposes. The ability to manipulate or erase critical business logic artifacts without detection undermines the integrity and reliability of the AI-driven features provided by the platform.
From a threat modeling perspective, this vulnerability aligns with MITRE ATT&CK technique T1078, Valid Accounts, as it leverages legitimate credentials to perform unauthorized actions, and specifically relates to data destruction capabilities often associated with insider threats or compromised accounts seeking to cause damage rather than exfiltrate information. The attack vector is straightforward, requiring only a valid session token and knowledge of the target record's identifier, which may be discoverable through enumeration attacks if other endpoints leak such identifiers in list views or error messages.
To mitigate this vulnerability, developers must implement strict object-level authorization checks within the delete handler logic before executing any database deletion commands. This involves querying the database to retrieve the owner and tenant information associated with the specified id parameter and comparing it against the authenticated user's identity and assigned tenant context. If these values do not match exactly, the request should be rejected with an appropriate HTTP 403 Forbidden response. Additionally, implementing comprehensive logging for all deletion attempts can aid in detecting potential abuse patterns post-exploitation. Upgrading to a patched version of JeecgBoot that addresses this access control flaw is essential for restoring security posture and ensuring data integrity across the application ecosystem.