CVE-2026-66001
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,…
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (0.23%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
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.
- CVSS 4.0
- 8.5 HIGHCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/M
- EPSS
- 0.23% probability · 14th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-352
- Source
- security-advisories@github.com
References
- https://github.com/frappe/frappe/commit/336c7d335db762b494acdfe43aea69d459fd51d7
- https://github.com/frappe/frappe/commit/d7460769f999c68d3121b680119f8724ddd3eb9d
- https://github.com/frappe/frappe/commit/eb9c1446cac13236c6d573b136786db2e46254fa
- https://github.com/frappe/frappe/pull/40073
- https://github.com/frappe/frappe/pull/40700
- https://github.com/frappe/frappe/pull/40701
- https://github.com/frappe/frappe/releases/tag/v15.114.0
- https://github.com/frappe/frappe/releases/tag/v16.26.0
- https://github.com/frappe/frappe/security/advisories/GHSA-2ph8-x773-8p2x
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.