CVE-2018-20061
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 · uneditedA SQL injection issue was discovered in ERPNext 10.x and 11.x through 11.0.3-beta.29. This attack is only available to a logged-in user; however, many ERPNext sites allow account creation via the web. No special privileges are needed to conduct the attack. By calling a JavaScript function that calls a server-side Python function with carefully chosen arguments, a SQL attack can be carried out which allows SQL queries to be constructed to return any columns from any tables in the database. This is related to /api/resource/Item?fields= URIs, frappe.get_list, and frappe.call.
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 confidenceSQL injection vulnerability in ERPNext 10.x-11.x allows authenticated users to inject arbitrary SQL via the fields parameter in /api/resource/Item and similar URIs. The frappe.get_list function does not properly sanitize the fields parameter, enabling attackers to construct queries returning any columns from any tables.
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>= 10.0.0, <= 10.1.76>= 11.0.0, < 11.0.3= 11.0.3CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed ERPNext versionRun 'bench version' in the ERPNext/Frappe bench directory, or check the erpnext Python package version with 'pip show erpnext' or 'bench get-app-version erpnext'Affected if The version is >= 10.0.0 and <= 10.1.76, OR >= 11.0.0 and < 11.0.3, OR exactly 11.0.3
-
Confirm Frappe framework versionRun 'bench version' or check the frappe Python package version with 'pip show frappe' as ERPNext depends on FrappeAffected if Running alongside a vulnerable ERPNext version from the affected ranges above
-
Verify API endpoint accessibilityCheck if the web server is running and the /api/resource/ URI path is accessible. Look for the site configuration in sites/[sitename]/site_config.json and confirm webserver statusAffected if The ERPNext web interface or API is exposed and reachable
-
Check for authenticated user accessReview user account configurations and API key/token setups. The vulnerability requires an authenticated session to exploit the /api/resource/Item endpointAffected if Any user accounts exist in the system that could be leveraged for authenticated API access to the vulnerable endpoint
Your environment is affected if ERPNext version falls within 10.0.0 to 10.1.76, 11.0.0 to 11.0.2, or exactly 11.0.3, AND the web/API interface is accessible with authenticated user accounts.
Generated from the published advisory. Verify against your own configuration.
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 data11.0.3
Upgrade ERPNext to a patched version that properly sanitizes the fields parameter in frappe.get_list and related API endpoints. Implement parameterized queries or whitelist-based field validation.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-20061 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-20061 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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