LiveActive security incident?Get immediate response
CVE Record

CVE-2018-3885: An exploitable SQL injection vulnerability exists in the authenticated part of ERPNext v10.1.6.

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.

MediumCVSS 5.4Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

ERPNext v10.1.6 has an authenticated SQL injection issue. A logged-in user could send crafted web requests through the order_by parameter and potentially access or change application data. The public sources do not show active exploitation or a named fixed version.

Executive priority

Treat this as a moderate data-risk issue. It requires authentication, which lowers urgency, but ERP systems often contain sensitive financial and operational data. Prioritize inventory and upgrade planning, especially for internet-facing deployments.

Technical view

CVE-2018-3885 affects the authenticated portion of ERPNext v10.1.6 (master). The order_by parameter is injectable, with CVSS 3.0 score 5.4: network reachable, low attack complexity, low privileges required, no user interaction, and low confidentiality and integrity impact.

Likely exposure

Exposure is limited to organizations running ERPNext v10.1.6 where authenticated users can reach the vulnerable functionality. Risk increases if many users have accounts, accounts are weakly protected, or ERPNext is internet-accessible.

Exploitation context

The CVE is not listed as KEV in the provided bundle. Talos describes browser-triggered exploitation requiring no special tools, but the sources provided do not establish active exploitation in the wild.

Researcher notes

The source bundle names ERPNext v10.1.6 (master), the authenticated attack surface, and order_by as the vulnerable parameter. It does not provide CWE mapping, a fixed version, exploit-in-the-wild evidence, or detailed remediation steps.

Mitigation direction

  • Inventory ERPNext deployments and identify any v10.1.6 instances.
  • Check ERPNext/Frappe and Talos guidance for the fixed or recommended version.
  • Upgrade affected ERPNext instances after confirming vendor guidance.
  • Restrict ERPNext access to trusted users and networks where practical.
  • Review account hygiene and remove unnecessary ERPNext user access.

Validation and detection

  • Confirm the running ERPNext version on all relevant environments.
  • Review access logs for suspicious order_by parameter activity.
  • Check database logs for unusual authenticated query patterns.
  • Verify exposed ERPNext instances require authentication and MFA where available.
  • Document whether any vulnerable v10.1.6 instance remains in production.
Prepared
Confidence
medium
Sources
3

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-3885 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.0MediumCVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

5.4Medium
CVSS 3.0 vector shape for CVE-2018-3885Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
TalosERPNextERPNext v10.1.6 (master)Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.