CVE-2018-3885: SQL Injection
First published: Wed Sep 12 2018(Updated: )
An exploitable SQL injection vulnerability exists in the authenticated part of ERPNext v10.1.6. Specially crafted web requests can cause SQL injections resulting in data compromise. The order_by parameter can be used to perform an SQL injection attack. An attacker can use a browser to trigger these vulnerabilities, and no special tools are required.
Credit: talos-cna@cisco.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| ERPNext | =10.1.6 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What severity level is CVE-2018-3885?
CVE-2018-3885 has a high severity level due to its potential for data compromise via SQL injection.
How do I fix CVE-2018-3885?
To fix CVE-2018-3885, upgrade ERPNext to a version beyond 10.1.6 that has addressed this vulnerability.
What type of vulnerability is CVE-2018-3885?
CVE-2018-3885 is an SQL injection vulnerability that affects the authenticated part of ERPNext.
Which version of ERPNext is affected by CVE-2018-3885?
CVE-2018-3885 specifically affects ERPNext version 10.1.6.
What can an attacker do with CVE-2018-3885?
An attacker can exploit CVE-2018-3885 to perform SQL injection attacks, potentially leading to unauthorized data access.
- agent/type
- agent/softwarecombine
- agent/severity
- agent/author
- agent/weakness
- agent/references
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/erpnext
- canonical/erpnext
- version/erpnext/10.1.6