XXE (XML External Entity) in ERPNext (CVE-2026-44445)
Summary
Vulnerability in ERPNext (CVE-2026-44445). Confidential information can be exposed externally. 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.12.0, an improper restriction of XML external entity (XXE) reference vulnerability in the EDI Module enables an authenticated attacker to read files from the local file system, including sensitive configuration files. This vulnerability is fixed in 15.104.3 and 16.12.0.
Source: NIST National Vulnerability Database NVD
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-44445 has been found in ERPNext.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade ERPNext to 15.104.3 or later.
If unsure, ask your IT team or search "ERPNext CVE-2026-44445" on the vendor's site.
CVE-2026-44445 (ERPNext) — CWE-611 / CVSS v3 6.5
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.
A vulnerability (CWE-611) exists in ERPNext.
Check the vendor advisory for the affected versions of ERPNext.
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.
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 でアラート再発が無いか継続監視。