dbcve.org
FrappeApplication

CVE-2026-31877

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-11
Fix available
A fix is available. Upgrade to 14.99.0 / 15.84.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 15.84.0 and 14.99.0, a specially crafted request made to a certain endpoint could result in SQL injection, allowing an attacker to extract information they wouldn't otherwise be able to. This vulnerability is fixed in 15.84.0 and 14.99.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 15.84.0 and 14.99.0 contain a SQL injection vulnerability in a specific endpoint. Attackers can send specially crafted requests containing malicious SQL queries to extract sensitive database information they wouldn't normally access.

MitigationUpgrade Frappe to version 15.84.0 or 14.99.0 or later to apply the security patch. Until then, restrict network access to vulnerable endpoints as a temporary measure.

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:< 14.99.0>= 15.0.0, < 15.84.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. Identify the installed Frappe version
    Run the command 'bench version' in the Frappe bench directory, or check the version file at /workspace/frappe-bench/sites/[site_name]/site_config.json if accessible via CLI
    Affected if The version returned is below 14.99.0 OR is 15.0.0 through 15.83.x
  2. Confirm the exact version number
    Cross-reference the version from step 1 with Frappe release notes or the git tags in the Frappe repository to ensure accurate comparison to the affected ranges
    Affected if The version cannot be determined or does not match a known released version in the affected ranges
  3. Determine if the vulnerable API endpoint is exposed
    Review the Frappe web server configuration and routing setup to identify if the specific SQL injection-vulnerable endpoint is accessible externally versus localhost-only
    Affected if The vulnerable endpoint is reachable from network locations outside the local server
  4. Check network access controls to Frappe
    Inspect firewall rules, reverse proxy configuration (nginx/apache), and Frappe site settings to assess whether the web interface is exposed to untrusted networks
    Affected if Frappe is accessible from the internet or untrusted internal networks without authentication proxies

A user is affected if their Frappe installation version is below 14.99.0 or falls between 15.0.0 and 15.83.x AND the vulnerable endpoint is network-accessible.

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 14.99.0 / 15.84.0 or later
Fixed in 14.99.015.84.0
Interim mitigation

Upgrade Frappe to version 15.84.0 or 14.99.0 or later to apply the security patch. Until then, restrict network access to vulnerable endpoints as a temporary measure.

Recommended fix High confidence

14.99.0 for v14.x branches; 15.84.0 for v15.x branches

  1. Identify your current Frappe version by checking your application's version file or bench CLI output
  2. If running Frappe version 14.x: Upgrade to version 14.99.0 or later
  3. If running Frappe version 15.x: Upgrade to version 15.84.0 or later
  4. After upgrading, verify the installation was successful and test critical functionality
  5. Review release notes for the target version to ensure all dependencies are met
Caveat Review version-specific release notes for any deprecations or breaking changes between your current version and the target fixed version

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

Fix this in Frappe Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
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,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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