dbcve.org
ErpnextApplication · Frappe

CVE-2026-44445

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-13
Fix available
A fix is available. Upgrade to 15.104.3 / 16.12.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

ERPNext versions prior to 15.104.3 and 16.12.0 contain an XXE vulnerability in the EDI (Electronic Data Interchange) module that allows authenticated users to read files from the local file system, including sensitive configuration files, by crafting malicious XML with external entity references.

MitigationUpgrade ERPNext to version 15.104.3 or 16.12.0 or later, which includes proper XML external entity restriction in the EDI module's parser.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ErpnextApplication
Affected:< 15.104.3>= 16.0.0, < 16.12.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check ERPNext version
    Run 'bench version' or check the Help > About ERPNext page to find the installed version
    Affected if Version is below 15.104.3 or >= 16.0.0 and below 16.12.0
  2. Verify EDI module status
    Navigate to: Modules > EDI or check Module configuration to see if Electronic Data Interchange is enabled
    Affected if EDI module is installed and active in the system
  3. Inspect XML import functionality in EDI
    Go to the EDI module and look for XML file import/upload features that process incoming EDI documents
    Affected if XML import/upload capability exists in the EDI module and is accessible to authenticated users
  4. Check user roles with EDI access
    Review User permissions (Setup > Users > Permissions) to see which roles have access to the EDI module
    Affected if Authenticated users have role-based access to create or import documents in the EDI module

A system is affected if it runs an affected ERPNext version AND has the EDI module enabled with XML processing capability accessible to authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 15.104.3 / 16.12.0 or later
Fixed in 15.104.316.12.0
Interim mitigation

Upgrade ERPNext to version 15.104.3 or 16.12.0 or later, which includes proper XML external entity restriction in the EDI module's parser.

Recommended fix High confidence

ERPNext 15.104.3+ or 16.12.0+ (depending on major version branch)

  1. 1. Identify the current ERPNext version by checking the site configuration or running `bench version`.
  2. 2. For ERPNext version 15.x: Upgrade to version 15.104.3 or later by running `bench switch-to-branch version-15` and then `bench update --upgrade`.
  3. 3. For ERPNext version 16.x: Upgrade to version 16.12.0 or later by running `bench switch-to-branch version-16` and then `bench update --upgrade`.
  4. 4. After upgrade, verify the EDI module functions correctly and test that XXE vulnerability is no longer exploitable.
  5. 5. Review and restart the Frappe/ERPNext services if necessary using `bench restart`.
Caveat Standard ERPNext upgrade risks apply - test in staging first, review custom apps compatibility, and backup database before production upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Erpnext Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44445 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44445 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data