{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-3885 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-3885 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-3885 is a medium-severity SQL injection vulnerability in Frappe Erpnext, published on 12 Sep 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-3885 and fix it if it is affected.\n\nWhat it is: CVE-2018-3885 is a medium-severity SQL injection vulnerability in Frappe Erpnext, published on 12 Sep 2018. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-3885 in the wild and no public exploit code.\n\nAffected product: Frappe Erpnext. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2018-3885/ (Markdown: https://insights.sbomify.com/CVE-2018-3885/index.md)","id":"CVE-2018-3885","markdown":"https://insights.sbomify.com/CVE-2018-3885/index.md","name":"CVE-2018-3885","record":{"aliases":["GHSA-5x9m-2fcv-3q75"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"ERPNext","requires_auth":"low_privilege","summary":"Authenticated attackers can exploit SQL injection in ERPNext via the order_by parameter to compromise data integrity and confidentiality.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"erpnext","vendor":"frappe"}],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"SQL injection in ERPNext","id":"CVE-2018-3885","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"frappe:erpnext","products":["frappe:erpnext"],"type":"sql_injection","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in Computerinsel Photoline","id":"CVE-2018-3886"},"packages":[],"prev":{"headline":"SQL injection in ERPNext","id":"CVE-2018-3884"},"products":["ERPNext"],"published":"2018-09-12","related":[{"cvss_score":9.9,"headline":"ERPNext: Unauthorised Document modification due to missing validation","id":"CVE-2026-44442","kev_date_added":null,"published":"2026-05-13"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2026-38431","kev_date_added":null,"published":"2026-05-05"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2025-66438","kev_date_added":null,"published":"2025-12-15"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-66439","kev_date_added":null,"published":"2025-12-15"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-66440","kev_date_added":null,"published":"2025-12-15"},{"cvss_score":9.6,"headline":"File upload in n/a","id":"CVE-2025-67289","kev_date_added":null,"published":"2025-12-22"},{"cvss_score":9.3,"headline":"ERP: Document access through endpoints due to missing validation","id":"CVE-2026-27471","kev_date_added":null,"published":"2026-02-21"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["Talos"]},"summary":"Authenticated attackers can exploit SQL injection in ERPNext via the order_by parameter to compromise data integrity and confidentiality.","url":"https://insights.sbomify.com/CVE-2018-3885/"}