EUVD-2026-30198Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privilege ERPNext account
-
DeliveryIdentify vulnerable endpoint
-
ExploitSend crafted request with SQL payload
-
ExecutionInject query into MariaDB backend
-
ImpactEnumerate and exfiltrate sensitive ERP data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires (1) network reachability to the ERPNext web interface and (2) valid low-privileged authentication to the ERPNext application (PR:L), which on many deployments includes self-service customer or supplier portal accounts. The vulnerable code path is reached via specially crafted requests to specific (vendor-undisclosed) endpoints in ERPNext versions below 16.9.0; no user interaction from another party is required (UI:N). Limiting factors: a valid account is mandatory so fully anonymous exploitation against a hardened instance with no portal registration is not possible, and the exact vulnerable endpoints have not been publicly disclosed in the advisory, raising the reverse-engineering effort needed to weaponize. |
| Impact | Signals are mixed and warrant nuanced prioritization. CVSS 8.8 with AV:N/AC:L/PR:L/UI:N/C:H/I:H/A:H suggests an authenticated user can fully compromise the database with low complexity - high inherent severity. However, EPSS is only 0.04% (12th percentile), SSVC exploitation status is 'none', SSVC marks the issue not automatable, and no POC is publicly identified, indicating no observed exploitation activity. SSVC technical impact is 'total', consistent with full DB compromise. The PR:L requirement is the main limiting factor: any low-privileged ERPNext account (including self-service portal users in some deployments) could be sufficient, which is a meaningful concern for multi-tenant or customer-portal instances. Priority should be high for internet-exposed or multi-tenant deployments, moderate for internal-only installs. |
| Exploit ScenarioDerived | An attacker with a low-privileged ERPNext account - for example, a customer-portal user on an internet-exposed instance - sends a crafted HTTP request to one of the vulnerable endpoints with malicious SQL payloads in parameters. The injected SQL executes against the MariaDB backend, allowing the attacker to enumerate tables and exfiltrate sensitive ERP data such as customer records, financial transactions, and credentials. No public POC has been identified at this time, but the bug class and CVSS profile make weaponization straightforward once endpoint details are reverse-engineered from the patch. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 08, 2026
SQL injection in ERPNext versions prior to 16.9.0 allows authenticated remote attackers to extract sensitive data by sending specially crafted requests to vulnerable endpoints. The Frappe-maintained ERP platform requires low-privileged authentication (PR:L) but has high impact on confidentiality, integrity, and availability per CVSS 8.8. No public exploit identified at time of analysis, and EPSS probability is very low (0.04%).
RemediationAI
Vendor-released patch: upgrade ERPNext to 16.9.0 or later, per the GitHub Security Advisory at https://github.com/frappe/erpnext/security/advisories/GHSA-q65v-fm9p-9vh3. For deployments that cannot patch immediately, restrict access to the ERPNext web interface using network ACLs or VPN-only access to reduce the pool of authenticated attackers, audit and disable unused low-privilege accounts (especially self-service portal/customer accounts), and enable database-level query logging or a WAF with SQLi signatures in front of the Frappe app server - noting that WAF rules may produce false positives against legitimate report-building queries and Frappe's report-builder API. Review database user privileges granted to the Frappe application user and apply least privilege where feasible, which will limit the blast radius but may break some ERPNext features that rely on broad DB access.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
ERPNext is an open-source Enterprise Resource Planning application built on the Frappe framework (Python/MariaDB stack), widely deployed for accounting, HR, inventory, and CRM workflows. The root cause is CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), meaning user-controlled input reaches the database query layer without adequate parameterization or sanitization. The affected CPE is cpe:2.3:a:frappe:erpnext, and the issue spans multiple endpoints rather than a single function, suggesting systemic input-handling gaps in request processing rather than a one-off bug.
Know when Erpnext gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Primary rating from GitHub Advisory · only source for this CVE.
CVSS VectorGitHub Advisory
Lifecycle Timeline
1DescriptionGitHub Advisory
ERPNext is a free and open source Enterprise Resource Planning tool. Prior to 16.9.0, some endpoints were vulnerable to SQL injection through specially crafted requests, which would allow a malicious actor to extract sensitive information. This vulnerability is fixed in 16.9.0.
Executive ViewAI
ERPNext deployments running versions prior to 16.9.0 are vulnerable to SQL injection attacks that allow authenticated users to extract or modify sensitive business data (CVE-2026-44447, CVSS 8.8). The vulnerability requires valid user credentials to exploit but carries high impact to data confidentiality and integrity. Organizations must prioritize upgrading to version 16.9.0 or later to eliminate this risk.
Apply vendor patch: ERPNext 16.9.0 or later.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
GitHub
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
Stored cross-site scripting leading to code execution in Frappe Framework 15.89.0 (and the ERPNext application built on
An exploitable SQL injection vulnerability exists in the authenticated part of ERPNext v10.1.6. Rated high severity (CVS
An exploitable SQL injection vulnerability exists in the authenticated part of ERPNext v10.1.6. Rated high severity (CVS
An exploitable SQL injection vulnerability exists in the authenticated part of ERPNext v10.1.6. Rated high severity (CVS
An exploitable SQL injection vulnerability exists in the authenticated part of ERPNext v10.1.6. Rated high severity (CVS
Authenticated SQL injection in Frappe ERPNext through 15.89.0 allows low-privilege users to extract arbitrary database c
SQL injection in Frappe ERPNext through 15.89.0 lets an authenticated attacker with a valid session and access to the Pa
Authenticated attackers with permission to create or modify Print Format documents in Frappe ERPNext through 15.89.0 can
Authenticated server-side template injection in Frappe ERPNext through 15.89.0 lets a user who can create or modify an A
Authenticated server-side template injection in Frappe ERPNext through 15.89.0 allows users with privileges to configure
An SQL injection vulnerability exists in the frappe.desk.reportview.get functionality of ERPNext 11.1.38. Rated high sev
Frappe Framework ERPNext 13.4.0 contains a sandbox escape vulnerability in RestrictedPython that allows authenticated us
Exploit-DB