CVE-2026-134431 in ERPNextinfo

Summary

by MITRE • 11/21/2026

Frappe ERPNext 7.0.0 before 15.122.0 and 16.x before 16.50.0 contains an SQL injection vulnerability in endpoints that build part of a query from caller-supplied sort parameters without validation. Authenticated low-privilege users can send crafted requests whose sort parameter holds SQL that the database executes as part of the query, extracting sensitive information.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Analysis

by VulDB Data Team • 11/21/2026

The identified security flaw resides within Frappe ERPNext versions prior to 7.0.0 before build 15.122.0 and version 16.x prior to release 16.50.0, representing a critical SQL injection vulnerability in the application's query construction logic. This specific weakness affects endpoints that dynamically generate database queries based on user-supplied sort parameters provided by the client during request processing. The core technical failure is the absence of proper input validation or parameterization for these sorting fields, allowing an attacker to inject arbitrary Structured Query Language commands directly into the execution context of the database engine.

From a technical perspective, this vulnerability exploits the way the framework constructs SQL statements using string concatenation rather than prepared statements when handling order-by clauses. When a user requests data sorted by a specific column or expression, the application incorporates that input directly into the final query string without sanitization. This allows an authenticated attacker with low-privilege access to manipulate the database structure of the request. By crafting malicious sort parameters containing SQL syntax such as UNION SELECT statements or boolean-based blind injection techniques, the attacker can bypass intended data isolation and extract sensitive information from underlying tables that should remain inaccessible under normal operational conditions.

The operational impact of this vulnerability is significant due to its potential for unauthorized data exfiltration. Although exploitation requires authentication, the requirement for low-privilege access lowers the barrier to entry for attackers who may have obtained credentials through phishing or credential stuffing attacks. Once authenticated, an attacker can leverage this flaw to read sensitive business data including customer records, financial transactions, employee details, and proprietary configuration settings stored within the ERPNext database. This compromise undermines the confidentiality integrity of the entire enterprise resource planning system potentially leading to regulatory violations under frameworks such as GDPR or HIPAA depending on the nature of the exposed data.

This vulnerability aligns with Common Weakness Enumeration identifier CWE-89 which classifies Improper Neutralization of Special Elements used in an SQL Command, commonly known as SQL Injection. In terms of offensive security mapping it corresponds to ATT&CK technique T1059 which covers Command and Scripting Interpreter abuse specifically within the context of database interaction where attackers use injected commands to achieve unauthorized access or data extraction. The lack of input validation on dynamic query components represents a fundamental design flaw that persists across multiple major versions indicating a systemic issue in how sorting parameters are handled throughout the codebase rather than an isolated incident.

Mitigation strategies must prioritize immediate patching as the primary defense vector. Organizations running affected versions should upgrade to Frappe ERPNext version 15.122.0 or later for the seven series and version 16.50.0 or later for the sixteen series where this issue has been addressed through improved input validation and parameterized query construction. In environments where immediate patching is not feasible due to compatibility constraints, temporary mitigations include implementing a Web Application Firewall rule set that detects and blocks SQL injection patterns within sort parameters specifically targeting order-by clauses in HTTP requests. Additionally restricting database user permissions to the principle of least privilege can limit the extent of damage if an exploitation attempt succeeds by preventing elevated operations such as dropping tables or accessing system schemas even if data extraction occurs.

Responsible

VulnCheck

Reservation

11/21/2026

Disclosure

11/21/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Do you need the next level of professionalism?

Upgrade your account now!