CVE-2026-134371 in Frappe
Summary
by MITRE • 11/21/2026
Frappe 8.8.0 before 16.30.0 contains an insecure direct object reference vulnerability in the SMS Settings get_contact_number API that lets attackers read any Contact's phone numbers without permission checks. Attackers can call the endpoint, which uses an uncorrelated EXISTS subquery, to retrieve mobile_no and phone values of arbitrary Contact records, exposing PII.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Analysis
by VulDB Data Team • 11/21/2026
The vulnerability identified in Frappe versions prior to 16.30.0 represents a critical failure in access control mechanisms within the SMS Settings module. Specifically, the get_contact_number API endpoint is susceptible to an Insecure Direct Object Reference (IDOR) flaw. This type of vulnerability arises when an application exposes internal implementation objects, such as database records or file paths, directly to users without adequate authorization checks. In this specific instance, the API allows any authenticated user to retrieve sensitive personal information by manipulating input parameters that reference Contact records. The core technical deficiency lies in the backend logic which fails to verify whether the requesting user has permission to access the specific contact data being requested. Instead of validating ownership or role-based permissions against the target resource, the system relies on an uncorrelated EXISTS subquery structure. This architectural choice means the query executes without properly binding the current session's identity or privileges to the scope of the retrieved records, effectively bypassing intended security boundaries and allowing unrestricted read access to phone numbers associated with arbitrary Contact entities.
From a technical perspective, the use of an uncorrelated EXISTS subquery in this context is particularly problematic because it does not inherently restrict results based on user-specific criteria unless explicitly coded into the query conditions. In many database-driven applications, developers may assume that wrapping data retrieval in certain SQL constructs provides implicit security or performance benefits without realizing that these structures do not automatically enforce row-level security policies. Consequently, an attacker can simply provide a valid identifier for any Contact record within the system and receive its associated mobile_no and phone values back from the server. This behavior constitutes a classic case of broken access control where the application does not sufficiently verify authorization before fulfilling requests to manipulate or retrieve data belonging to other users. The lack of permission checks means that even if a user is logged in, they are treated as having full administrative privileges regarding contact information retrieval, regardless of their actual role or assigned permissions within the Frappe environment.
The operational impact of this vulnerability is significant due to the nature of the exposed data. Phone numbers constitute Personally Identifiable Information (PII) and are often used for two-factor authentication, account recovery, and direct communication channels. Unauthorized access to these details can lead to severe privacy violations and facilitate further malicious activities such as phishing campaigns, SIM swapping attacks, or targeted social engineering against employees or customers of organizations using the Frappe platform. For businesses relying on this software for customer relationship management or internal communications, the exposure of contact lists undermines trust and may result in non-compliance with data protection regulations such as GDPR or CCPA. The ability to scrape large volumes of phone numbers efficiently could also enable spamming operations or credential stuffing attacks if those numbers are linked to other compromised accounts elsewhere on the internet.
To mitigate this vulnerability, immediate action is required by upgrading the Frappe framework to version 16.30.0 or later where these access control issues have been addressed. For organizations unable to upgrade immediately, implementing a web application firewall rule that restricts access to the SMS Settings API endpoints can provide temporary relief, although this is not a substitute for fixing the underlying code logic. Developers should review all API endpoints involved in data retrieval and ensure they implement strict authorization checks before executing database queries. This includes verifying that the requesting user owns the resource or has explicit permission to view it. Additionally, refactoring the SQL queries to use correlated subqueries where appropriate can help bind query execution more tightly to specific user contexts, reducing the risk of unintended data leakage. Regular security audits and penetration testing focused on access control flaws are recommended to identify similar weaknesses in other parts of the application before they can be exploited by malicious actors.
This vulnerability aligns with CWE-639, which describes Insecure Direct Object Reference vulnerabilities where a program uses user-supplied input to access objects directly without proper authorization checks. It also maps to MITRE ATT&CK technique T1078, specifically the Valid Accounts subcategory, as exploitation requires valid authentication but abuses those credentials to perform unauthorized data exfiltration. Understanding these mappings helps security teams prioritize remediation efforts and communicate the severity of the issue to stakeholders using standardized industry terminology. By addressing both the immediate code defect and the broader architectural approach to authorization, organizations can significantly reduce their attack surface and protect sensitive user information from unauthorized disclosure.