{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-66435 exists.","fix":"No fix has been published for CVE-2025-66435 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-66435 is a medium-severity code injection vulnerability in Frappe Erpnext, published on 15 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-66435 and fix it if it is affected.\n\nWhat it is: CVE-2025-66435 is a medium-severity code injection vulnerability in Frappe Erpnext, published on 15 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-66435 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-66435/ (Markdown: https://insights.sbomify.com/CVE-2025-66435/index.md)","id":"CVE-2025-66435","markdown":"https://insights.sbomify.com/CVE-2025-66435/index.md","name":"CVE-2025-66435","record":{"aliases":["GHSA-hc98-xxm8-jfgj"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"ERPNext","requires_auth":"low_privilege","summary":"Authenticated attackers can execute arbitrary code and leak database information by injecting Jinja2 templates into contract terms in ERPNext.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"erpnext","vendor":"frappe"}],"cvss":{"score":4.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"},{"id":"CWE-1336","name":"Improper Neutralization of Special Elements Used in a Template Engine"}],"description":"An SSTI (Server-Side Template Injection) vulnerability exists in the get_contract_template method of Frappe ERPNext through 15.89.0. The function renders attacker-controlled Jinja2 templates (contract_terms) using frappe.render_template() with a user-supplied context (doc). Although Frappe uses a custom SandboxedEnvironment, several dangerous globals such as frappe.db.sql are still available in the execution context via get_safe_globals(). An authenticated attacker with access to create or modify a Contract Template can inject arbitrary Jinja expressions into the contract_terms field, resulting in server-side code execution within a restricted but still unsafe context. This vulnerability can be used to leak database information.","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":"Code injection in n/a","id":"CVE-2025-66435","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"frappe:erpnext","products":["frappe:erpnext"],"type":"code_injection","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Code injection in n/a","id":"CVE-2025-66436"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2025-66434"},"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-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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-17","vendors":["n/a"]},"summary":"Authenticated attackers can execute arbitrary code and leak database information by injecting Jinja2 templates into contract terms in ERPNext.","url":"https://insights.sbomify.com/CVE-2025-66435/"}