VulnerabilityPublished 6 Sep 2025Updated 8 Sep 2025

CVE-2025-58439: frappe erpnext · SQL Injection

Affects frappe erpnextSource CVE Database V5

Not known to be exploited · CVSS 8.1 High : upgrade to 14.89.2 soon.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

8.1High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 14.89.2

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade frappe erpnext to 14.89.2.

Affected software

Product	Affected	Fixed in
frappe erpnext	Affected <14.89.2	Fixed in 14.89.2

AI-suggested

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.

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.

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.

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 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.

CWE-89Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #2OWASP Top 10 A05:2025: Injection (opens in a new tab)
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.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Parameterization
If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.
Architecture and Design · Operation · Environment Hardening
Run your code using the lowest privileges that are required to accomplish the necessary tasks. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment.
OWASP Cheat Sheets
Query Parameterization (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
XML Security (opens in a new tab)
XML External Entity Prevention (opens in a new tab)
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.4 (opens in a new tab)
V5.3.5 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
Command Line Execution through SQL Injection (opens in a new tab)
Object Relational Mapping Injection (opens in a new tab)
SQL Injection through SOAP Parameter Tampering (opens in a new tab)
Expanding Control over the Operating System from the Database (opens in a new tab)
SQL Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 13 Sep 2025, 03:43 UTC

WeaknessesCWE-89

Technical details

References

Community reviews

Related threats