CVE-2026-66001

Published: Ago 20, 2026 Last Modified: Ago 20, 2026
ExploitDB:
Other exploit source:
Google Dorks:
HIGH 8,5
Attack Vector: network
Attack Complexity: low
Privileges Required: none
User Interaction: active
Confidentiality: N/A
Integrity: N/A
Availability: N/A

Description

AI Translation Available

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.

352

Cross-Site Request Forgery (CSRF)

Stable
Common Consequences
Security Scopes Affected:
Confidentiality Integrity Availability Non-Repudiation Access Control
Potential Impacts:
Gain Privileges Or Assume Identity Bypass Protection Mechanism Read Application Data Modify Application Data Dos: Crash, Exit, Or Restart
Applicable Platforms
Technologies: Web Based, Web Server
View CWE Details
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