CVE-2024-7045 in open-webui
Summary
by MITRE • 03/20/2025
In version v0.3.8 of open-webui/open-webui, improper access control vulnerabilities allow an attacker to view any prompts. The application does not verify whether the attacker is an administrator, allowing the attacker to directly call the /api/v1/prompts/ interface to retrieve all prompt information created by the admin, which includes the ID values. Subsequently, the attacker can exploit the /api/v1/prompts/command/{command_id} interface to obtain arbitrary prompt information.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Analysis
by VulDB Data Team • 08/14/2026
The vulnerability identified as CVE-2024-7045 affects the open-webui/open-webui application version 0.3.8 and represents a critical improper access control flaw that fundamentally undermines the application's security model. This vulnerability stems from inadequate authorization checks within the application's API endpoints, specifically targeting the prompt management functionality. The flaw exists in the authentication and authorization mechanisms that should prevent unauthorized access to administrative resources, creating a pathway for attackers to bypass normal security boundaries and access sensitive information that should be restricted to privileged users only.
The technical implementation of this vulnerability manifests through the application's failure to properly validate user privileges when accessing the /api/v1/prompts/ endpoint. When an attacker makes a request to this interface, the system does not verify whether the requesting user possesses administrative privileges before returning prompt data. This oversight allows any authenticated user to retrieve all prompt information created by administrators, including sensitive ID values that serve as keys to additional attack vectors. The vulnerability extends beyond simple data exposure, as the exposed prompt IDs can be leveraged to exploit the secondary /api/v1/prompts/command/{command_id} interface, enabling attackers to obtain arbitrary prompt information through direct API calls.
The operational impact of this vulnerability is severe and multifaceted, as it provides attackers with comprehensive access to the application's prompt database without requiring administrative credentials or elevated privileges. This access can lead to information disclosure of sensitive prompt configurations, command structures, and potentially reveal system architecture details that could aid in further exploitation. The vulnerability can be exploited through simple API requests, making it particularly dangerous as it requires minimal technical expertise to execute. Attackers can systematically enumerate prompt information, potentially identifying command patterns that may reveal system functionalities or even sensitive operational procedures embedded within the prompts.
This vulnerability aligns with CWE-285, which addresses improper authorization issues in software systems, and represents a clear violation of the principle of least privilege that should govern all application interfaces. The attack pattern follows the MITRE ATT&CK framework's privilege escalation and credential access tactics, as attackers can leverage this vulnerability to gain unauthorized access to administrative resources that should remain protected. Organizations using this application are at risk of exposure to attackers who can extract sensitive operational data, potentially leading to more sophisticated attacks that exploit the revealed prompt structures and command patterns. The vulnerability also represents a failure in the application's defense in depth strategy, where multiple layers of security should have prevented such unauthorized access to administrative resources.
Mitigation strategies should focus on implementing robust authentication and authorization controls within the application's API endpoints, ensuring that all administrative interfaces require proper privilege validation before returning sensitive data. The application should enforce role-based access control mechanisms that verify user permissions before granting access to prompt information. Additionally, implementing proper input validation and output filtering can help prevent attackers from exploiting the exposed ID values to enumerate additional resources. Regular security audits and penetration testing should be conducted to identify similar authorization flaws in other API endpoints, while maintaining up-to-date security patches and implementing proper monitoring for unauthorized access attempts to administrative resources.