CVE-2025-58439
BaseFortify
Publication date: 2025-09-06
Last updated on: 2025-10-27
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| frappe | erpnext | to 14.89.2 (exc) |
| frappe | erpnext | From 15.0.0 (inc) to 15.76.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is an error-based SQL injection in the ERPNext software, caused by lack of validation of parameters in certain endpoints. Attackers can exploit this flaw by sending specially crafted inputs to these endpoints, which allows them to execute unauthorized SQL commands on the database. This can lead to retrieval of sensitive information such as software version details. The vulnerability affects versions below 14.89.2 and 15.0.0 through 15.75.1 and is fixed in versions 14.89.2 and 15.76.0. [1]
How can this vulnerability impact me? :
This vulnerability can have a high impact as it allows attackers to remotely exploit the system with low complexity and minimal privileges, without any user interaction. The attacker can gain unauthorized access to sensitive data (high confidentiality impact) and potentially modify data (high integrity impact). However, it does not affect system availability. Exploitation could lead to data breaches and unauthorized data manipulation within the affected ERP system. [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate step to mitigate this vulnerability is to upgrade the ERPNext software to version 14.89.2 or 15.76.0, where the issue has been fixed by replacing raw SQL queries with a safer query builder approach and implementing input sanitization to prevent SQL injection. No workarounds exist, so upgrading is required to address the vulnerability. [1, 2, 3]