CVE-2026-66001 Frappe: Improper Authorization in OAuth2 Consent Endpoint
Attackers can trick authenticated users into approving OAuth grants or reusing authorization state, exposing data and permitting unauthorized actions.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2026-66001?
CVE-2026-66001 is a high-severity vulnerability in frappe, published on 20 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official 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.
Weakness: CWE-352
Which versions are affected by CVE-2026-66001?
How do I fix CVE-2026-66001?
No fix has been published for CVE-2026-66001 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-66001 being exploited?
There is no known exploitation of CVE-2026-66001 in the wild and no public exploit code.
Sources
Also known as GHSA-2ph8-x773-8p2x.