Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-58439: CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in frappe erpnext

0
High
VulnerabilityCVE-2025-58439cvecve-2025-58439cwe-89
Published: Sat Sep 06 2025 (09/06/2025, 00:30:26 UTC)
Source: CVE Database V5
Vendor/Project: frappe
Product: erpnext

Description

ERP is a free and open source Enterprise Resource Planning tool. In versions below 14.89.2 and 15.0.0 through 15.75.1, lack of validation of parameters left certain endpoints vulnerable to error-based SQL Injection. Some information like version could be retrieved. This issue is fixed in versions 14.89.2 and 15.76.0.

AI-Powered Analysis

AILast updated: 09/13/2025, 03:43:01 UTC

Technical Analysis

CVE-2025-58439 is a high-severity SQL Injection vulnerability affecting the open-source Enterprise Resource Planning (ERP) software ERPNext, developed by the Frappe framework. The vulnerability exists in versions prior to 14.89.2 and from 15.0.0 up to 15.75.1. It arises due to improper neutralization of special elements in SQL commands (CWE-89), specifically a lack of validation or sanitization of input parameters in certain API endpoints. This flaw allows an attacker with at least low-level privileges (PR:L) to craft malicious input that can manipulate backend SQL queries, leading to error-based SQL Injection. Through this, attackers can extract sensitive information such as version details and potentially other confidential data from the database. The vulnerability does not require user interaction and can be exploited remotely over the network (AV:N) with low attack complexity (AC:L). The impact affects confidentiality and integrity but not availability, as the CVSS vector indicates no impact on availability. The issue has been addressed in ERPNext versions 14.89.2 and 15.76.0. No known exploits have been reported in the wild yet, but the high CVSS score of 8.1 underscores the criticality of timely patching. Given ERPNext’s role in managing enterprise resources, financial data, and operational workflows, exploitation could lead to significant data breaches and unauthorized data manipulation.

Potential Impact

For European organizations using ERPNext, this vulnerability poses a significant risk to the confidentiality and integrity of sensitive business data, including financial records, customer information, and operational details. Successful exploitation could lead to unauthorized data disclosure, potentially violating GDPR and other data protection regulations, resulting in legal and financial penalties. The integrity compromise could disrupt business processes by allowing attackers to alter data, leading to operational inefficiencies or fraudulent activities. Since ERPNext is often used by SMEs and larger enterprises across Europe for critical business functions, the impact could be widespread. Additionally, the lack of known exploits currently does not preclude future attacks, especially as threat actors often target ERP systems due to their rich data stores and central role in business operations.

Mitigation Recommendations

European organizations should immediately verify their ERPNext version and upgrade to 14.89.2 or 15.76.0 or later to remediate the vulnerability. Beyond patching, organizations should implement strict input validation and parameter sanitization on all endpoints, especially those exposed externally. Employing Web Application Firewalls (WAFs) with SQL Injection detection rules can provide an additional layer of defense. Conduct thorough code reviews and penetration testing focused on injection flaws in custom ERPNext extensions or integrations. Restrict ERPNext access to trusted networks and enforce the principle of least privilege for user accounts to minimize the risk of exploitation by low-privilege attackers. Regularly monitor logs for unusual query errors or suspicious activities indicative of attempted SQL Injection. Finally, ensure that backups are current and tested to enable recovery in case of data integrity compromise.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
GitHub_M
Date Reserved
2025-09-01T20:03:06.532Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68bb8705535f4a97731c0bc1

Added to database: 9/6/2025, 12:57:41 AM

Last enriched: 9/13/2025, 3:43:01 AM

Last updated: 10/21/2025, 4:23:07 AM

Views: 68

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats