{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-66439 exists.","fix":"No fix has been published for CVE-2025-66439 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-66439 is a critical SQL injection vulnerability in Frappe Erpnext, published on 15 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-66439 and fix it if it is affected.\n\nWhat it is: CVE-2025-66439 is a critical SQL injection vulnerability in Frappe Erpnext, published on 15 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-66439 exists.\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-2025-66439/ (Markdown: https://insights.sbomify.com/CVE-2025-66439/index.md)","id":"CVE-2025-66439","markdown":"https://insights.sbomify.com/CVE-2025-66439/index.md","name":"CVE-2025-66439","record":{"aliases":["GHSA-6329-q89j-9c7m"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"ERPNext","requires_auth":"none","summary":"An attacker can extract arbitrary database data via SQL injection in the payment entry module of ERPNext.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"erpnext","vendor":"frappe"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"An issue was discovered in Frappe ERPNext through 15.89.0. Function get_outstanding_reference_documents() at erpnext.accounts.doctype.payment_entry.payment_entry.py is vulnerable to SQL Injection. It allows an attacker to extract arbitrary data from the database by injecting SQL payloads via the from_posting_date parameter, which is directly interpolated into the query without proper sanitization or parameter binding.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"SQL injection in n/a","id":"CVE-2025-66439","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"frappe:erpnext","products":["frappe:erpnext"],"type":"sql_injection","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"SQL injection in n/a","id":"CVE-2025-66440"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2025-66438"},"products":["n/a"],"published":"2025-12-15","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-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":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-12-16","vendors":["n/a"]},"summary":"An attacker can extract arbitrary database data via SQL injection in the payment entry module of ERPNext.","url":"https://insights.sbomify.com/CVE-2025-66439/"}