SQL Injection in ERPNext (CVE-2026-44446)
Summary
SQL injection in ERPNext (CVE-2026-44446). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 15.104.3 or later.
Original description
The description as published by the source.
ERPNext is a free and open source Enterprise Resource Planning tool. Prior to 15.104.3 and 16.14.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 15.104.3 and 16.14.0.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44446 has been found in ERPNext.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade ERPNext to 15.104.3 or later.
If unsure, ask your IT team or search "ERPNext CVE-2026-44446" on the vendor's site.
CVE-2026-44446 (ERPNext) — CWE-89 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Patched: 15.104.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SQL injection (CWE-89) exists in ERPNext.
Check the vendor advisory for the affected versions of ERPNext.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to 15.104.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'ERPNext' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'ERPNext' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
ERPNextを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade ERPNext to 15.104.3ステージング環境で 15.104.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov