Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-32954: CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in frappe erpnext

0
High
VulnerabilityCVE-2026-32954cvecve-2026-32954cwe-89
Published: Fri Mar 20 2026 (03/20/2026, 04:30:26 UTC)
Source: CVE Database V5
Vendor/Project: frappe
Product: erpnext

Description

CVE-2026-32954 is a high-severity SQL injection vulnerability affecting the open-source ERP system ERPNext versions prior to 16. 8. 0 and 15. 100. 0. The flaw arises from improper neutralization of special elements in SQL commands, enabling time-based and boolean-based blind SQL injection attacks. Exploiting this vulnerability allows attackers with low privileges to infer sensitive database information without requiring user interaction. Although no known exploits are currently reported in the wild, the vulnerability poses a significant risk to confidentiality. The issue has been addressed in ERPNext versions 16. 8.

AI-Powered Analysis

AILast updated: 03/20/2026, 05:08:54 UTC

Technical Analysis

CVE-2026-32954 is a vulnerability classified under CWE-89, indicating improper neutralization of special elements used in SQL commands, commonly known as SQL injection. This flaw affects ERPNext, a widely used free and open-source Enterprise Resource Planning (ERP) software developed by Frappe. Specifically, versions prior to 16.8.0 and 15.100.0 contain certain endpoints that do not sufficiently validate input parameters before incorporating them into SQL queries. This improper validation allows attackers to perform time-based and boolean-based blind SQL injection attacks. Such attacks do not directly reveal data but enable attackers to infer sensitive information from the database by observing response times or boolean conditions. The vulnerability requires the attacker to have low-level privileges (PR:L) but does not require user interaction (UI:N), and it can be exploited remotely over the network (AV:N). The CVSS v3.1 base score of 7.1 reflects a high severity due to the high impact on confidentiality, limited impact on availability, and no impact on integrity. The vulnerability has been fixed in ERPNext versions 16.8.0 and 15.100.0 by improving parameter validation and sanitization to prevent injection of malicious SQL code. No public exploit code or active exploitation has been reported to date, but the potential for data leakage remains significant if unpatched systems are exposed.

Potential Impact

The primary impact of CVE-2026-32954 is the unauthorized disclosure of sensitive database information due to blind SQL injection attacks. Organizations running vulnerable versions of ERPNext risk exposure of confidential business data, including financial records, customer information, and internal operational data. Although the vulnerability does not allow direct modification or deletion of data, the confidentiality breach can facilitate further attacks such as privilege escalation, data exfiltration, or social engineering. The attack requires only low privileges and no user interaction, increasing the likelihood of exploitation in exposed environments. The availability impact is low, but the loss of confidentiality can severely damage organizational reputation, compliance posture, and operational security. Given ERPNext’s use in diverse industries worldwide, the vulnerability could affect a broad range of sectors including manufacturing, retail, healthcare, and education.

Mitigation Recommendations

To mitigate CVE-2026-32954, organizations should immediately upgrade ERPNext installations to versions 16.8.0 or 15.100.0 or later, where the vulnerability has been patched. In addition to patching, organizations should implement strict input validation and sanitization on all user-supplied data, especially on endpoints that interact with the database. Employing web application firewalls (WAFs) with SQL injection detection rules can provide an additional layer of defense against exploitation attempts. Regularly audit and monitor database query logs for unusual patterns indicative of blind SQL injection attempts, such as repeated time delays or boolean-based probing. Restrict database user privileges to the minimum necessary to limit the potential impact of injection attacks. Finally, conduct security awareness training for developers and administrators to ensure secure coding practices and timely application of security updates.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-03-17T00:05:53.285Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69bcd2fce32a4fbe5f2df42a

Added to database: 3/20/2026, 4:54:20 AM

Last enriched: 3/20/2026, 5:08:54 AM

Last updated: 3/20/2026, 7:12:52 AM

Views: 6

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses