Frappe Framework CVE-2025-68929

Exploitation requires an authenticated Frappe user who holds 'specific permissions' (per the advisory) and who must be socially engineered into opening a specially crafted link that carries a server-side template payload - this is the concrete precondition, not a default-configuration remote attack. The principal limiting factors are: (1) valid authentication at a non-trivial permission level (PR:L), and (2) mandatory victim interaction (UI:R) - the privileged user must actively click/access the attacker's link for the malicious template to render. These two gates substantially narrow realistic exploitation to targeted social-engineering of existing privileged accounts rather than opportunistic mass exploitation. No workaround exists; only upgrading to 14.99.6 (v14 branch) or 15.88.1 (v15 branch) remediates it.

This is a genuine high-priority vulnerability but short of 'drop everything' emergency status, and the signals are largely consistent. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H, base 9.0) reflects a server-side template injection that yields full remote code execution with scope change - meaning compromise extends from the Frappe application to the underlying OS. However, two CVSS metrics meaningfully constrain real-world risk: PR:L requires the attacker to already have an authenticated account with 'specific permissions' (per the description), and UI:R requires tricking that privileged user into clicking a crafted link, making this a social-engineering-dependent, semi-targeted attack rather than a point-and-shoot remote exploit. The exploitation-likelihood signals corroborate a lower urgency than the 9.0 suggests: EPSS is only 0.50% (41st percentile), there is no CISA KEV listing, and no public exploit code was identified in the provided intelligence. The combination of a critical technical-impact score with low EPSS and no observed exploitation indicates a serious-but-not-yet-actively-weaponized flaw - patch promptly, but it does not carry the same immediacy as an unauthenticated, no-interaction KEV-listed RCE. No SSVC decision data was provided in the input, so that framework cannot be applied here.

An attacker who holds (or phishes) a Frappe account with the requisite permissions crafts a malicious link embedding a server-side template payload and lures a privileged victim into opening it. When the victim's authenticated session processes the link, the malicious Jinja/template content is rendered server-side, executing attacker-controlled code on the Frappe host. No public proof-of-concept was identified in the provided data, and UI:R means the chain depends on successfully social-engineering the victim into clicking.