dbcve.org
FrappeApplication

CVE-2026-35614

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-07
Fix available
A fix is available. Upgrade to 15.104.0 / 16.14.0 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Frappe is a full-stack web application framework. Prior to 16.14.0 and 15.104.0, Frappe has a SQL injection in bulk_update. This vulnerability is fixed in 16.14.0 and 15.104.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

Frappe framework versions prior to 16.14.0 and 15.104.0 contain a SQL injection vulnerability in the bulk_update function. This allows attackers to inject malicious SQL queries through the bulk_update endpoint, potentially leading to unauthorized database access, data exfiltration, or complete system compromise.

MitigationUpgrade Frappe framework to version 16.14.0 or 15.104.0 or later to apply the security patch that fixes the SQL injection in bulk_update.

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
FrappeApplication
Affected:< 15.104.0>= 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
High
Availability
High

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

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 installed Frappe version
    Run 'bench version' or inspect the frappe package version via 'pip show frappe' or the version file in the Frappe installation directory
    Affected if The version displayed is below 15.104.0, OR is 16.0.0 or higher but below 16.14.0
  2. Identify Frappe major version line
    Determine whether your deployment follows the Frappe 15 or Frappe 16 release line by checking the version output from the previous step
    Affected if You are on Frappe version 15.x below 15.104.0, or on Frappe version 16.x below 16.14.0
  3. Locate bulk_update endpoint exposure
    Check if the bulk_update API endpoint is accessible by reviewing your Frappe site's API routes, typically under /api/method/ for bulk_update or related client methods
    Affected if The bulk_update endpoint is exposed and reachable without additional compensating controls
  4. Verify bulk_update function implementation
    Search the Frappe source code for the bulk_update function definition, typically in client.py or a related module, and verify if it directly incorporates user-supplied data into SQL queries without proper sanitization
    Affected if The bulk_update function exists in the codebase and processes input without parameterized queries or ORM escaping

You are affected if your Frappe installation version is below 15.104.0 or falls between 16.0.0 and 16.14.0, and the bulk_update endpoint is accessible in your environment.

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.0 / 16.14.0 or later
Fixed in 15.104.016.14.0
Interim mitigation

Upgrade Frappe framework to version 16.14.0 or 15.104.0 or later to apply the security patch that fixes the SQL injection in bulk_update.

Recommended fix High confidence

15.104.0 (for v15.x) or 16.14.0 (for v16.x)

  1. 1. Identify your current Frappe version by checking the installed version in your environment
  2. 2. If running Frappe 15.x: upgrade to version 15.104.0
  3. 3. If running Frappe 16.x: upgrade to version 16.14.0
  4. 4. Use your package manager or Frappe's bench command to perform the upgrade (e.g., bench switch-to-branch or pip install with specific version)
  5. 5. After upgrade, verify the new version is installed correctly
  6. 6. Test that the bulk_update functionality works as expected
  7. 7. Review release notes for any additional migration steps required
Caveat Review Frappe release notes between your current version and the target version for any breaking changes or database migrations

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

Fix this in Frappe Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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