Skip to main content

Erpnext CVE-2026-32954

| EUVDEUVD-2026-13547 HIGH
SQL Injection (CWE-89)
2026-03-20 security-advisories@github.com
7.1
CVSS 3.1 · GitHub Advisory
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate to ERP application
  2. Exploit
    Send malicious SQL payload to vulnerable endpoint
  3. Execution
    Execute time-based blind SQL injection queries
  4. Impact
    Infer database structure and sensitive 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

Requires authenticated user access to ERP versions prior to 16.8.0 and 15.100.0. Attacker must be a logged-in user with access to vulnerable endpoints. Remote exploitation over network. No victim interaction required. Blind SQL injection enables database information disclosure.

Impact

The CVSS score of 7.1 (High) reflects network-accessible exploitation with low attack complexity, requiring only low privileges and no user interaction, with high confidentiality impact and low availability impact. The attack vector (AV:N) indicates remote exploitation is possible, while PR:L means an authenticated account is required, reducing the attack surface compared to unauthenticated vulnerabilities. The integrity impact is rated None, suggesting the primary concern is data exfiltration rather than modification. Given that ERPNext systems typically contain sensitive business data including financial records, customer information, and proprietary business intelligence, the confidentiality impact is significant for organizations using this platform. The availability of patches in versions 15.100.0 and 16.8.0 provides clear remediation paths. While no EPSS score or KEV listing is provided in the intelligence data and no public proof-of-concept is explicitly mentioned, the SQL injection vulnerability class is well-understood and easily exploitable by moderately skilled attackers once endpoints are identified. Real-world risk is elevated for internet-facing ERPNext installations with multiple user accounts, particularly those handling sensitive business data, making this a priority for organizations running affected versions.

Exploit ScenarioDerived

An authenticated attacker with low-level user credentials (such as a basic employee account) accesses vulnerable ERPNext endpoints and submits crafted requests containing SQL injection payloads designed to manipulate the underlying database queries. By leveraging time-based injection techniques, the attacker measures response delays to infer whether specific conditions are true or false, systematically extracting sensitive information such as administrator credentials, financial data, customer records, or proprietary business information character by character. The network-accessible nature and low attack complexity mean this can be automated and executed remotely without requiring physical access or complex exploit chains.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 20, 2026

A blind SQL injection vulnerability exists in ERPNext, a free and open-source Enterprise Resource Planning system, affecting versions prior to 15.100.0 and beta versions 16.0.0-beta.1 through 16.7.x. The vulnerability allows authenticated attackers with low-level privileges to perform time-based and boolean-based blind SQL injection attacks through insufficiently validated parameters on certain endpoints, enabling them to infer and extract sensitive database information. This is tagged as an SQLi vulnerability and has been assigned EUVD-2026-13547 by ENISA, with patches available in versions 15.100.0 and 16.8.0.

RemediationAI

Organizations running ERPNext should immediately upgrade to version 15.100.0 or later for the version 15 release line, or to version 16.8.0 or later for those on version 16 beta releases, as documented in the official releases at https://github.com/frappe/erpnext/releases/tag/v15.100.0 and https://github.com/frappe/erpnext/releases/tag/v16.8.0. Review the complete security advisory at https://github.com/frappe/erpnext/security/advisories/GHSA-j669-ghv2-gmqg for specific details about the affected endpoints and fixes. Until patching is completed, implement defense-in-depth measures including restricting ERPNext access to trusted IP ranges via firewall rules, enforcing strong authentication policies to minimize the risk from compromised low-privilege accounts, enabling comprehensive SQL query logging to detect exploitation attempts, and conducting a security audit to identify any unauthorized data access that may have occurred prior to patching.

Affected VersionsENISA

ERPNext < 15.100.0
ERPNext 16.0.0-beta.1, < 16.8.0

Affected Packages

euvd erpnext fix: 15.100.0
euvd erpnext_16_0_0_beta_1 fix: 16.8.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 2 packages 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 a comprehensive open-source ERP solution built on the Frappe framework that manages business operations including accounting, inventory, and human resources. This vulnerability is classified as CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), commonly known as SQL injection. The affected endpoints failed to properly sanitize or parameterize user-supplied input before incorporating it into SQL queries, allowing attackers to manipulate query logic through crafted payloads. Blind SQL injection techniques—both time-based (measuring response delays to infer true/false conditions) and boolean-based (observing application behavior changes)—enable attackers to extract database contents character by character without direct error messages or output, making detection more challenging than traditional SQL injection.

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

GitHub Advisory PRIMARY 7.1 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

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

Lifecycle Timeline

2
Patch available
Apr 16, 2026 - 05:29 EUVD
15.100.0,16.8.0
CVE Published
Mar 20, 2026 - 05:16 nvd
HIGH 7.1

DescriptionGitHub Advisory

ERP is a free and open source Enterprise Resource Planning tool. In versions prior to 16.8.0 and 15.100.0, certain endpoints were vulnerable to time-based and boolean-based blind SQL injection due to insufficient parameter validation, allowing attackers to infer database information. This issue has been fixed in versions 15.100.0 and 16.8.0.

Executive ViewAI

Why It Matters

ERPNext versions before 15.100.0 and 16.x before 16.8.0 contain a blind SQL injection vulnerability allowing authenticated users with low privileges to extract sensitive database information, potentially compromising confidential business data stored in the ERP system. Organizations running affected versions face risk of unauthorized data disclosure and require immediate patching to prevent exploitation by internal or compromised user accounts.

Business Impact: High
Compensating Controls

Apply vendor patch. If immediate patching is not feasible: restrict database access at the application layer to read-only for low-privilege accounts where possible, implement network segmentation isolating ERP database from non-critical systems, and deploy Web Application Firewall rules to block SQL injection payloads on affected endpoints.

Threat Intelligence Overview

EPSS Score
0.0%
Top 92% exploitable
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GitHub VulDB

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Partial

Priority Score

36
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

CVE-2025-67289 CRITICAL POC
9.6 Dec 22

Stored cross-site scripting leading to code execution in Frappe Framework 15.89.0 (and the ERPNext application built on

CVE-2018-3885 HIGH POC
8.8 Sep 12

An exploitable SQL injection vulnerability exists in the authenticated part of ERPNext v10.1.6. Rated high severity (CVS

CVE-2018-3884 HIGH POC
8.8 Sep 12

An exploitable SQL injection vulnerability exists in the authenticated part of ERPNext v10.1.6. Rated high severity (CVS

CVE-2018-3883 HIGH POC
8.8 Sep 12

An exploitable SQL injection vulnerability exists in the authenticated part of ERPNext v10.1.6. Rated high severity (CVS

CVE-2018-3882 HIGH POC
8.8 Sep 12

An exploitable SQL injection vulnerability exists in the authenticated part of ERPNext v10.1.6. Rated high severity (CVS

CVE-2025-66440 HIGH POC
8.8 Dec 15

Authenticated SQL injection in Frappe ERPNext through 15.89.0 allows low-privilege users to extract arbitrary database c

CVE-2025-66439 HIGH POC
8.8 Dec 15

SQL injection in Frappe ERPNext through 15.89.0 lets an authenticated attacker with a valid session and access to the Pa

CVE-2025-66438 HIGH POC
8.8 Dec 15

Authenticated attackers with permission to create or modify Print Format documents in Frappe ERPNext through 15.89.0 can

CVE-2025-66437 HIGH POC
8.8 Dec 15

Authenticated server-side template injection in Frappe ERPNext through 15.89.0 lets a user who can create or modify an A

CVE-2025-66434 HIGH POC
8.8 Dec 15

Authenticated server-side template injection in Frappe ERPNext through 15.89.0 allows users with privileges to configure

CVE-2020-6145 HIGH POC
8.8 Aug 10

An SQL injection vulnerability exists in the frappe.desk.reportview.get functionality of ERPNext 11.1.38. Rated high sev

CVE-2023-54345 HIGH POC
8.7 May 05

Frappe Framework ERPNext 13.4.0 contains a sandbox escape vulnerability in RestrictedPython that allows authenticated us

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy