dbcve.org
FrappeApplication

CVE-2025-66205

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-01
Fix available
A fix is available. Upgrade to 14.99.2 / 15.86.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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.86.0 and 14.99.2, a certain endpoint was vulnerable to error-based SQL injection due to lack of validation of parameters. Some information like version could be retrieved. This vulnerability is fixed in 15.86.0 and 14.99.2.

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 web application framework contains an error-based SQL injection vulnerability in a certain endpoint due to lack of parameter validation. Attackers can craft malicious input to trigger SQL errors that reveal sensitive information such as database version details.

MitigationUpgrade Frappe to version 15.86.0 or 14.99.2 or later to apply the parameter validation fix that addresses the SQL injection vulnerability.

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.2>= 15.0.0, < 15.86.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 installed Frappe version
    Run 'bench version' in the Frappe bench directory, or check the version file at /frappe-bench/sites/[site-name]/site_config.json for the 'frappe_version' field
    Affected if Version is below 14.99.2, or is 15.0.0 through 15.85.x (15.86.0 and later are patched)
  2. Confirm Frappe is running
    Check if the Frappe web service is active by accessing your site URL or running 'bench status'
    Affected if Frappe web interface is accessible (required for the vulnerable endpoint to be reachable)
  3. Verify network exposure of Frappe endpoints
    Review firewall rules or load balancer configuration to determine if the Frappe web interface is exposed to unauthenticated network access from untrusted IPs
    Affected if The Frappe instance is reachable from the internet or untrusted networks without authentication controls, allowing unauthenticated attackers to reach the vulnerable endpoint

Your environment is affected if the installed Frappe version is below 14.99.2 or falls between 15.0.0 and 15.85.x, and the web interface is network-accessible to unauthenticated 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 14.99.2 / 15.86.0 or later
Fixed in 14.99.215.86.0
Vendor patch github.com →
Interim mitigation

Upgrade Frappe to version 15.86.0 or 14.99.2 or later to apply the parameter validation fix that addresses the SQL injection vulnerability.

Recommended fix High confidence

14.99.2 for v14 branch, or 15.86.0 for v15 branch

  1. Identify current Frappe version by checking the deployed release (e.g., via bench version or pip show frappe)
  2. If running Frappe 14.x branch: Plan upgrade to version 14.99.2
  3. If running Frappe 15.x branch: Plan upgrade to version 15.86.0
  4. Run full backup of database and files before upgrade
  5. Update Frappe using bench: bench get-app frappe https://github.com/frappe/frappe.git --version 14.99.2 or 15.86.0 as appropriate
  6. Run bench migrate after update to apply database changes
  7. Verify the application functions correctly after migration
  8. Test that the SQL injection vulnerability is no longer present
Caveat Review Frappe release notes between current version and target version for any breaking changes or deprecated features; major version jumps may require additional migration steps

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

Fix this in Frappe Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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