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

> Authenticated attackers can inject Jinja expressions into Print Formats to leak database information via exposed SQL functions.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Dec 2025
- **Updated:** 16 Dec 2025
- **Also known as:** GHSA-5x94-7mhw-9ff6

## What is CVE-2025-66438?

CVE-2025-66438 is a critical code 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.

### Official description

A Server-Side Template Injection (SSTI) vulnerability exists in the Frappe ERPNext through 15.89.0 Print Format rendering mechanism. Specifically, the API frappe.www.printview.get_html_and_style() triggers the rendering of the html field inside a Print Format document using frappe.render_template(template, doc) via the get_rendered_template() call chain. Although ERPNext wraps Jinja2 in a SandboxedEnvironment, it exposes sensitive functions such as frappe.db.sql through get_safe_globals(). An authenticated attacker with permission to create or modify a Print Format can inject arbitrary Jinja expressions into the html field. Once the malicious Print Format is saved, the attacker can call get_html_and_style() with a target document (e.g., Supplier or Sales Invoice) to trigger the render process. This leads to information disclosure from the database, such as database version, schema details, or sensitive values, depending on the injected payload. Exploitation flow: Create a Print Format with SSTI payload in the html field; call the get_html_and_style() API; triggers frappe.render_template(template, doc) inside get_rendered_template(); leaks database information via frappe.db.sql or other exposed globals.

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-66438?

It affects 1 product.


Products: Frappe Erpnext.

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

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

## Is CVE-2025-66438 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-66438 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-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)
- [CVE-2025-67289](https://insights.sbomify.com/CVE-2025-67289/): File upload in n/a (critical 9.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-66438 is a critical code 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-66438 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-66438/ (Markdown: https://insights.sbomify.com/CVE-2025-66438/index.md)
```

## Sources

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

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