# CVE-2018-20061: SQL injection in n/a

> A logged-in user can execute arbitrary SQL queries via crafted API requests, allowing unauthorized access to any database table columns.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-66f4-g2vx-q58x

## What is CVE-2018-20061?

CVE-2018-20061 is a high-severity SQL injection vulnerability in Frappe Erpnext, published on 11 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A 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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2018-20061?

It affects 1 product.


Products: Frappe Erpnext.

## How do I fix CVE-2018-20061?

No fix has been published for CVE-2018-20061 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-20061 being exploited?

There is no known exploitation of CVE-2018-20061 in the wild and no public exploit code.

## Other vulnerabilities in Frappe Erpnext

- [CVE-2026-44442](https://insights.sbomify.com/CVE-2026-44442/): ERPNext: Unauthorised Document modification due to missing validation (critical 9.9)
- [CVE-2026-38431](https://insights.sbomify.com/CVE-2026-38431/): Code injection in n/a (critical 9.8)
- [CVE-2025-66438](https://insights.sbomify.com/CVE-2025-66438/): Code injection in n/a (critical 9.8)
- [CVE-2025-66439](https://insights.sbomify.com/CVE-2025-66439/): SQL injection in n/a (critical 9.8)
- [CVE-2025-66440](https://insights.sbomify.com/CVE-2025-66440/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-20061 and fix it if it is affected.

What it is: CVE-2018-20061 is a high-severity SQL injection vulnerability in Frappe Erpnext, published on 11 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-20061 in the wild and no public exploit code.

Affected product: Frappe Erpnext. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-20061/ (Markdown: https://insights.sbomify.com/CVE-2018-20061/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-20061
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-20061
- OSV: https://osv.dev/vulnerability/CVE-2018-20061

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-20061/
Summaries are generated and may contain mistakes; the official description above is the record.