dbcve.org
FrappeApplication

CVE-2017-1000120

HIGH · 8.8 CVSS v3.0 Published 2017-10-05
Fix available
A fix is available. Upgrade to after 7.1.27 or later.
See remediation →
94/100
Remediation priority · Urgent
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][Frappe Version <= 7.1.27] SQL injection vulnerability in frappe.share.get_users allows remote authenticated users to execute arbitrary SQL commands via the fields parameter.

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

SQL injection vulnerability in frappe.share.get_users in Frappe framework versions 7.1.27 and earlier allows remote authenticated users to execute arbitrary SQL commands through the fields parameter. The vulnerability stems from unsanitized user input being passed directly into SQL queries.

MitigationUpgrade Frappe framework to version > 7.1.27. As a temporary workaround, restrict access to the frappe.share.get_users endpoint and implement input validation on the fields parameter until the upgrade can be completed.

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:<= 7.1.27

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
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:L/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 Frappe framework installation
    Locate the Frappe installation by checking for the existence of the 'frappe' Python package directory or the 'frappe' command-line tool. Common paths include /frappe-bench/apps/frappe or the Python site-packages directory. Use 'pip show frappe' or 'bench version' if available.
    Affected if Frappe framework is not installed or cannot be identified.
  2. Determine installed Frappe version
    Run 'bench version' or check the Frappe version file (typically in frappe-bench/apps/frappe/frappe/__init__.py) to obtain the exact version number. Compare against the affected range: any version <= 7.1.27 is vulnerable.
    Affected if The installed Frappe version is 7.1.27 or earlier.
  3. Verify frappe.share.get_users method exists
    Check if the file containing frappe.share.get_users exists in the Frappe installation. This is typically located in frappe/share.py or share.py within the frappe module. Use file system search: find /path/to/frappe -name '*.py' -exec grep -l 'def get_users' {} \;
    Affected if The frappe.share.get_users method exists in the codebase.
  4. Confirm fields parameter handling
    Inspect the source code of the get_users function to verify whether the 'fields' parameter is used in SQL queries without sanitization. Search for SQL execution patterns (cursor.execute, frappe.db.sql) that incorporate the fields parameter directly.
    Affected if The fields parameter is passed directly into SQL queries without sanitization or parameterization.
  5. Check endpoint accessibility
    Determine if the get_users method is exposed via the Frappe REST API or whitelisted methods. Review the web.py or api.py files in the frappe module for @frappe.whitelist() decorators applied to get_users or related share functions.
    Affected if The frappe.share.get_users method is exposed as a whitelisted API endpoint accessible to authenticated users.

You are affected if Frappe framework version 7.1.27 or earlier is installed AND the frappe.share.get_users method is exposed as a whitelisted endpoint with unsanitized fields parameter handling.

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.

From vendor data
Upgrade available Upgrade to a release after 7.1.27
Interim mitigation

Upgrade Frappe framework to version > 7.1.27. As a temporary workaround, restrict access to the frappe.share.get_users endpoint and implement input validation on the fields parameter until the upgrade can be completed.

Fix this in Frappe Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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