CVE-2025-58439: CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in frappe erpnext
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 Analysis
Technical Summary
CVE-2025-58439 is a high-severity SQL Injection vulnerability affecting the open-source Enterprise Resource Planning (ERP) software ERPNext, developed by the frappe project. The vulnerability exists in versions prior to 14.89.2 and between 15.0.0 and 15.75.1 inclusive. The root cause is improper neutralization of special elements used in SQL commands (CWE-89), specifically due to insufficient validation of input parameters on certain endpoints. This flaw allows an attacker with at least low-level privileges (PR:L) to perform error-based SQL Injection attacks remotely (AV:N) without requiring user interaction (UI:N). Exploiting this vulnerability can lead to disclosure of sensitive information such as version details, and potentially other confidential data stored in the backend database. The CVSS v3.1 base score is 8.1, reflecting high impact on confidentiality and integrity, with no impact on availability. The vulnerability is fixed in ERPNext versions 14.89.2 and 15.76.0 and later. No known exploits have been reported in the wild as of the publication date (September 6, 2025). Given ERPNext’s role in managing critical business processes including finance, inventory, and human resources, exploitation could compromise sensitive corporate data and disrupt business operations indirectly through data integrity loss or unauthorized data disclosure.
Potential Impact
For European organizations using ERPNext, this vulnerability poses a significant risk to the confidentiality and integrity of enterprise data. ERP systems typically contain sensitive financial records, personal employee information, supplier and customer data, and operational details. Successful exploitation could lead to unauthorized data disclosure, enabling industrial espionage, fraud, or regulatory non-compliance with GDPR and other data protection laws. Although availability is not directly impacted, data integrity loss could cause operational disruptions and financial inaccuracies. European companies in sectors such as manufacturing, retail, logistics, and professional services that rely on ERPNext for core business functions are particularly at risk. The vulnerability’s remote exploitability without user interaction increases the likelihood of automated attacks or targeted intrusions. Furthermore, the requirement for low-level privileges means that attackers who have gained minimal access through other means could escalate their impact significantly. The absence of known exploits in the wild provides a window for proactive patching and mitigation before widespread exploitation occurs.
Mitigation Recommendations
European organizations should immediately assess their ERPNext installations to determine if they are running affected versions below 14.89.2 or between 15.0.0 and 15.75.1. The primary mitigation is to upgrade ERPNext to version 14.89.2 or 15.76.0 or later, where the vulnerability is patched. Until upgrades can be applied, organizations should implement strict access controls to limit user privileges, especially restricting access to endpoints that accept user input for ERPNext. Network-level protections such as web application firewalls (WAFs) should be configured to detect and block SQL Injection patterns targeting ERPNext endpoints. Regularly auditing logs for suspicious query errors or anomalous database responses can help detect attempted exploitation. Additionally, organizations should review and harden input validation mechanisms in any custom ERPNext extensions or integrations. Conducting penetration testing focused on SQL Injection vectors in ERPNext environments can identify residual weaknesses. Finally, ensure backups are current and tested to enable recovery in case of data corruption or breach.
Affected Countries
Germany, France, United Kingdom, Netherlands, Italy, Spain, Poland, Sweden, Belgium, Austria
CVE-2025-58439: CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in frappe 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
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 project. The vulnerability exists in versions prior to 14.89.2 and between 15.0.0 and 15.75.1 inclusive. The root cause is improper neutralization of special elements used in SQL commands (CWE-89), specifically due to insufficient validation of input parameters on certain endpoints. This flaw allows an attacker with at least low-level privileges (PR:L) to perform error-based SQL Injection attacks remotely (AV:N) without requiring user interaction (UI:N). Exploiting this vulnerability can lead to disclosure of sensitive information such as version details, and potentially other confidential data stored in the backend database. The CVSS v3.1 base score is 8.1, reflecting high impact on confidentiality and integrity, with no impact on availability. The vulnerability is fixed in ERPNext versions 14.89.2 and 15.76.0 and later. No known exploits have been reported in the wild as of the publication date (September 6, 2025). Given ERPNext’s role in managing critical business processes including finance, inventory, and human resources, exploitation could compromise sensitive corporate data and disrupt business operations indirectly through data integrity loss or unauthorized data disclosure.
Potential Impact
For European organizations using ERPNext, this vulnerability poses a significant risk to the confidentiality and integrity of enterprise data. ERP systems typically contain sensitive financial records, personal employee information, supplier and customer data, and operational details. Successful exploitation could lead to unauthorized data disclosure, enabling industrial espionage, fraud, or regulatory non-compliance with GDPR and other data protection laws. Although availability is not directly impacted, data integrity loss could cause operational disruptions and financial inaccuracies. European companies in sectors such as manufacturing, retail, logistics, and professional services that rely on ERPNext for core business functions are particularly at risk. The vulnerability’s remote exploitability without user interaction increases the likelihood of automated attacks or targeted intrusions. Furthermore, the requirement for low-level privileges means that attackers who have gained minimal access through other means could escalate their impact significantly. The absence of known exploits in the wild provides a window for proactive patching and mitigation before widespread exploitation occurs.
Mitigation Recommendations
European organizations should immediately assess their ERPNext installations to determine if they are running affected versions below 14.89.2 or between 15.0.0 and 15.75.1. The primary mitigation is to upgrade ERPNext to version 14.89.2 or 15.76.0 or later, where the vulnerability is patched. Until upgrades can be applied, organizations should implement strict access controls to limit user privileges, especially restricting access to endpoints that accept user input for ERPNext. Network-level protections such as web application firewalls (WAFs) should be configured to detect and block SQL Injection patterns targeting ERPNext endpoints. Regularly auditing logs for suspicious query errors or anomalous database responses can help detect attempted exploitation. Additionally, organizations should review and harden input validation mechanisms in any custom ERPNext extensions or integrations. Conducting penetration testing focused on SQL Injection vectors in ERPNext environments can identify residual weaknesses. Finally, ensure backups are current and tested to enable recovery in case of data corruption or breach.
For access to advanced analysis and higher rate limits, contact root@offseq.com
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/6/2025, 1:12:34 AM
Last updated: 9/7/2025, 5:03:21 PM
Views: 23
Related Threats
CVE-2025-48042: CWE-863 Incorrect Authorization in ash-project ash
HighCVE-2025-10068: SQL Injection in itsourcecode Online Discussion Forum
MediumCVE-2025-10067: Cross Site Scripting in itsourcecode POS Point of Sale System
MediumCVE-2025-10066: Cross Site Scripting in itsourcecode POS Point of Sale System
MediumCVE-2025-36100: CWE-260 Password in Configuration File in IBM MQ
MediumActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.