dbcve.org
ErpnextApplication · Frappe

CVE-2026-44446

HIGH · 7.5 CVSS v3.1 Published 2026-05-13
Fix available
A fix is available. Upgrade to 15.104.3 / 16.14.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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.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.

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 contains SQL injection vulnerabilities in certain endpoints prior to versions 15.104.3 and 16.14.0. Attackers can exploit specially crafted requests to inject malicious SQL queries and extract sensitive information from the database. This is a classic SQL injection attack vector with high severity (CVSS 7.5).

MitigationUpgrade ERPNext to version 15.104.3 or 16.14.0 to receive the security patch. After upgrading, verify that the vulnerable endpoints have been remediated and conduct penetration testing to confirm the fix.

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.14.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 installed version
    Log into the ERPNext dashboard as Administrator, navigate to 'Help' > 'About', or run the command 'bench version' in the terminal where ERPNext is installed. Alternatively, check the 'apps.txt' file in the ERPNext installation directory.
    Affected if The version shown is below 15.104.3, OR the version is 16.x and below 16.14.0
  2. Verify Frappe framework version
    Run 'bench get-app frappe' or check the frappe version via the /api/method/frappe.utils.change_log.get_app_change_log endpoint, or inspect the version file in the frappe installation directory.
    Affected if The Frappe version corresponds to an ERPNext version that falls within the affected ranges (< 15.104.3 or >= 16.0.0, < 16.14.0)
  3. Identify exposed API endpoints
    Review the application's exposed API routes, particularly any custom or report-based endpoints that accept user input and query the database. Check for endpoints that do not use Frappe's standard parameterized query methods.
    Affected if The system has custom or third-party API endpoints that accept SQL-filtered parameters without proper input sanitization

You are affected if your ERPNext version is below 15.104.3 or falls between 16.0.0 and 16.14.0 (exclusive), and the vulnerable SQL injection endpoints are accessible on your network.

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.14.0 or later
Fixed in 15.104.316.14.0
Interim mitigation

Upgrade ERPNext to version 15.104.3 or 16.14.0 to receive the security patch. After upgrading, verify that the vulnerable endpoints have been remediated and conduct penetration testing to confirm the fix.

Recommended fix High confidence

Upgrade to ERPNext version 15.104.3 (for v15 installations) or 16.14.0 (for v16 installations)

  1. 1. Create a complete backup of the ERPNext database and all application files
  2. 2. Stop all ERPNext services (bench, workers, web server)
  3. 3. Navigate to the ERPNext bench directory (typically /home/frappe/bench or /opt/bench)
  4. 4. Run 'bench get-app erpnext' to fetch the latest version, or 'bench switch-to-branch' for specific version if using branch-based installation
  5. 5. For version 15.x: Run 'bench get-app erpnext https://github.com/frappe/erpnext --branch version-15 --overwrite' then 'bench update --patch'
  6. 6. For version 16.x: Run 'bench get-app erpnext https://github.com/frappe/erpnext --branch version-16 --overwrite' then 'bench update --patch'
  7. 7. Run database migrations with 'bench migrate'
  8. 8. Clear caches with 'bench clear-cache'
Caveat Major version upgrades may introduce breaking changes; review ERPNext release notes and test in staging environment before production deployment

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

Fix this in Erpnext Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44446 — 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-44446 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