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.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 1
- First seenCVSS 5.1NVD modified 2026-10-14 16:17
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 7
- 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