CSRF in Frappe

CVE-2026-66001

Frappe is a full-stack web application framework. Prior to 15.114.0 and 16.26.0, the approve and authorize functions in frappe/integrations/oauth2.py allow the OAuth2 consent flow to proceed without restricting approve to POST, without a csrf_token in frappe/templates/includes/oauth_confirmation.html, and without scoping an active OAuth token check to the requesting client. An attacker can cause an authenticated user to approve an OAuth grant or reuse authorization state for the wrong client, exposing data and permitting actions within the granted scopes. This issue is fixed in versions 15.114.0 and 16.26.0.

Vulnerability class: CSRF (Cross-Site Request Forgery)

Published · last modified .

EPSS exploit prediction

EPSS: 0.003 (25.2th percentile), scored .

Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 25th percentile — 25.2% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2026-66001: held from 0.002 to 0.003.

EPSS over last 30 days · oldest: 0.002 · newest: 0.003 · change: +0.001

Affected products

  • Frappe — versions < 15.114.0, >= 16.0.0-beta.1, < 16.26.0

Weakness classification (CWE)

References