# CVE-2025-66437: Code injection in n/a

> Authenticated attackers can execute arbitrary code or read database information by injecting Jinja expressions into Address Templates in Frappe ERPNext.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Dec 2025
- **Updated:** 16 Dec 2025
- **Also known as:** GHSA-36qq-9v26-crfg

## What is CVE-2025-66437?

CVE-2025-66437 is a high-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.

### Official description

An SSTI (Server-Side Template Injection) vulnerability exists in the get_address_display method of Frappe ERPNext through 15.89.0. This function renders address templates using frappe.render_template() with a context derived from the address_dict parameter, which can be either a dictionary or a string referencing an Address document. Although ERPNext uses a custom Jinja2 SandboxedEnvironment, dangerous functions like frappe.db.sql remain accessible via get_safe_globals(). An authenticated attacker with permission to create or modify an Address Template can inject arbitrary Jinja expressions into the template field. By creating an Address document with a matching country, and then calling the get_address_display API with address_dict="address_name", the system will render the malicious template using attacker-controlled data. This leads to server-side code execution or database information disclosure.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-1336 (Improper Neutralization of Special Elements Used in a Template Engine)

## Which versions are affected by CVE-2025-66437?

It affects 1 product.


Products: Frappe Erpnext.

## How do I fix CVE-2025-66437?

No fix has been published for CVE-2025-66437 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-66437 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-66437 exists.

## Other vulnerabilities in Frappe Erpnext

- [CVE-2026-44442](https://insights.sbomify.com/CVE-2026-44442/): ERPNext: Unauthorised Document modification due to missing validation (critical 9.9)
- [CVE-2026-38431](https://insights.sbomify.com/CVE-2026-38431/): Code injection in n/a (critical 9.8)
- [CVE-2025-66438](https://insights.sbomify.com/CVE-2025-66438/): Code injection in n/a (critical 9.8)
- [CVE-2025-66439](https://insights.sbomify.com/CVE-2025-66439/): SQL injection in n/a (critical 9.8)
- [CVE-2025-66440](https://insights.sbomify.com/CVE-2025-66440/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-66437 and fix it if it is affected.

What it is: CVE-2025-66437 is a high-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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-66437 exists.

Affected product: Frappe Erpnext. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-66437/ (Markdown: https://insights.sbomify.com/CVE-2025-66437/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-66437
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-66437
- OSV: https://osv.dev/vulnerability/CVE-2025-66437

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-66437/
Summaries are generated and may contain mistakes; the official description above is the record.