# CVE-2025-68929: Frappe may be vulnerable remote code execution due to server-side template injection

> An authenticated user can trigger remote code execution via server-side template injection by accessing a crafted link in the Frappe framework.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Dec 2025
- **Updated:** 29 Dec 2025
- **Also known as:** GHSA-qq98-vfv9-xmxh

## What is CVE-2025-68929?

CVE-2025-68929 is a critical code injection vulnerability in frappe, published on 29 Dec 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Frappe is a full-stack web application framework. Prior to versions 14.99.6 and 15.88.1, an authenticated user with specific permissions could be tricked into accessing a specially crafted link. This could lead to a malicious template being executed on the server, resulting in remote code execution. Versions 14.99.6 and 15.88.1 fix the issue. No known workarounds are available.

Weakness: CWE-1336 (Improper Neutralization of Special Elements Used in a Template Engine)

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

It affects 1 product.


Products: Frappe Frappe.

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

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

## Is CVE-2025-68929 being exploited?

There is no known exploitation of CVE-2025-68929 in the wild and no public exploit code.

## Other vulnerabilities in frappe

- [CVE-2019-14965](https://insights.sbomify.com/CVE-2019-14965/): Code injection in n/a (critical 9.8)
- [CVE-2026-35614](https://insights.sbomify.com/CVE-2026-35614/): Frappe has a SQL injection in bulk_update (critical 9.3)
- [CVE-2026-31877](https://insights.sbomify.com/CVE-2026-31877/): Frappe SQL Injection due to improper field sanitization (critical 9.3)
- [CVE-2019-14966](https://insights.sbomify.com/CVE-2019-14966/): SQL injection in n/a (high 8.8)
- [CVE-2017-1000120](https://insights.sbomify.com/CVE-2017-1000120/): SQL injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-68929 is a critical code injection vulnerability in frappe, published on 29 Dec 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-68929 in the wild and no public exploit code.

Affected product: frappe. 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-68929/ (Markdown: https://insights.sbomify.com/CVE-2025-68929/index.md)
```

## Sources

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

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