Frappe Framework EUVD-2026-36452

Exploitation requires the attacker to hold a valid Frappe user account with sufficient permissions to create or edit Notes in the target instance - typically any standard low-privilege role. The victim must subsequently navigate to and open the malicious Note in their browser session, providing the user-interaction trigger. Deployments where the Note feature is disabled or restricted exclusively to administrator roles have a substantially reduced attack surface. The reported CVSS 4.0 vector attributes PR:N and UI:N, which conflicts with these stored-XSS mechanics; defenders should treat PR:L and UI:P as the more accurate exploitation prerequisites pending vendor clarification. Frappe instances not accessible over the network or restricted to VPN-only access significantly limit reachability despite the AV:N classification.

The reported CVSS 4.0 score of 6.9 with vector AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N warrants scrutiny: a PR:N and UI:N rating is inconsistent with the stored XSS vulnerability class, which inherently requires at minimum victim browser interaction (UI:P in CVSS 4.0) and typically low privilege to author a Note (PR:L). This discrepancy likely inflates the automated score and reduces its reliability as a prioritization signal. EPSS at 0.02% (7th percentile) reflects very low observed exploitation probability, consistent with the absence of any CISA KEV listing or public proof-of-concept. Real-world risk is moderate in multi-tenant or shared Frappe deployments where a low-privileged user can create Notes visible to administrators or HR staff - session hijacking and privilege escalation via stolen tokens are the primary concern. The CVSS vector anomaly should be verified against the vendor advisory before using the NVD score for prioritization.

A low-privileged Frappe user - such as a standard employee account in an ERPNext deployment - creates a Note containing a crafted JavaScript payload embedded in an HTML attribute or script tag. When a higher-privileged user such as an HR manager or system administrator opens the note, the payload executes silently in their browser session, enabling cookie exfiltration or unauthorized API calls on their behalf. No public proof-of-concept has been identified, but the stored XSS technique is well-understood and requires no specialized tooling beyond a standard web browser.