CVE-2026-66057
5.1MediumPublished 13 Oct 2026 · NVD status: Deferred · AI triage by gemini-3.8-flash
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- Active
- Impact
- Limited impact
- Weakness
- CWE-601
Impact
Attackers can redirect authenticated users to arbitrary external sites for phishing or credential theft. They need the user to click a specially crafted OAuth login link.
Root cause
The OAuth login flow redirects users using an unsanitized, client-controlled state parameter without URL validation.
Affected systems
Frappe versions prior to 15.116.0 and 16.29.0
CVSS v4.0 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:N/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/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Fix & remediation
Upgrade Frappe to version 15.116.0 or 16.29.0 depending on your major release branch. No interim configuration mitigation is provided.
$ bench update --apps frappeAI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
Frappe is a full-stack web application framework. Prior to 15.116.0 and 16.29.0, the OAuth login flow uses an unsanitized client-controlled state parameter to select post-authentication navigation, allowing a crafted state value to redirect a user to an attacker-chosen location. This issue is fixed in versions 15.116.0 and 16.29.0.
References
- https://github.com/frappe/frappe/commit/12568e2d54c4abba70bc0261387053fa28f90988
- https://github.com/frappe/frappe/commit/1e0a3b941231d74a71ff1a43eee2e9f63c88712d
- https://github.com/frappe/frappe/commit/6ed8acd869199feb3a2598887d471448297edf07
- https://github.com/frappe/frappe/pull/40962
- https://github.com/frappe/frappe/releases/tag/v15.116.0
- https://github.com/frappe/frappe/releases/tag/v16.29.0
- https://github.com/frappe/frappe/security/advisories/GHSA-78c5-55xg-jm7m