Which versions of Frappe Framework are affected by CVE-2026-47194?

Frappe instances are vulnerable to account takeover via host header injection in magic login links, where unauthenticated attackers can redirect users to attacker-controlled domains to capture…. A patch is available.

How to fix or mitigate CVE-2026-47194?

Within 24 hours, identify all Frappe deployments and determine if magic login links are in use; if enabled, disable the feature immediately as a critical temporary measure to eliminate the attack surface. Within 7 days, implement Web Application Firewall (WAF) rules to reject requests with mismatched Host headers, configure email gateway filtering to flag outbound magic login links pointing to non-corporate domains, and require additional verification (SMS, security questions) for account recovery actions. Within 30 days, establish a patching timeline to upgrade to Frappe 15.108.0+ (v15 branch) or 16.18.3+ (v16 branch) once released by the vendor, test upgrades in staging, and execute production patching in phases to minimize disruption.

Frappe Framework CVE-2026-47194

Q: What is the CVSS score of CVE-2026-47194?

CVE-2026-47194 has a CVSS 4.0 base score of 8.6 (High). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/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/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.2%.

EUVD-2026-54158 HIGH

Origin Validation Error (CWE-346)

2026-08-06 security-advisories@github.com

Information Disclosure

8.6

CVSS 4.0 · Vendor: github

Severity by source

Vendor (github) PRIMARY

8.6 HIGH

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/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/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

8.1 HIGH

Network-reachable with no privileges to initiate magic link; victim click required (UI:R); account takeover yields high C and I; no availability impact.

3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (github).

CVSS VectorVendor: github

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Scope

Lifecycle Timeline

Patch available

Aug 06, 2026 - 23:03 EUVD

Analysis Generated

Aug 06, 2026 - 23:01 vuln.today

CVE Published

Aug 06, 2026 - 22:17 cve.org

HIGH 8.6

DescriptionCVE.org

Frappe is a full-stack web application framework. Prior to 15.108.0 and 16.18.3, temporary magic login link generation can use an attacker-controlled request Host header, allowing a remote attacker to cause emailed login links to point to an attacker-controlled domain and capture the login token when a recipient follows the link. This issue is fixed in versions 15.108.0 and 16.18.3.

AnalysisAI

Host header injection in Frappe's magic login link generation exposes users to account takeover via authentication token hijacking. Frappe versions prior to 15.108.0 (v15 branch) and 16.18.3 (v16 branch) construct emailed magic login URLs using the attacker-controlled HTTP Host header, allowing an unauthenticated remote attacker to craft a request that causes the application to send a seemingly legitimate email containing a login link pointing to an attacker-controlled domain - capturing the one-time token when the recipient clicks. No public exploit is identified at time of analysis, but the attack requires no authentication and minimal technical complexity, making it accessible to a broad range of threat actors.

Technical ContextAI

Frappe is a Python-based full-stack web application framework (github.com/frappe/frappe) widely used to build business applications, most notably ERPNext. It implements passwordless 'magic link' authentication, generating short-lived tokenized URLs that are emailed to users for one-click login. The root cause is CWE-346 (Origin Validation Error): the framework trusts the HTTP Host request header when constructing the magic login URL without validating it against a server-defined authoritative hostname. In HTTP, the Host header is client-supplied and trivially spoofable; when an application uses it to build outbound URLs without verification, it becomes a vector for Host header injection. Affected versions span the v15 branch below 15.108.0 and the v16 branch below 16.18.3, as confirmed by GitHub Security Advisory GHSA-3w78-3cj3-p949.

RemediationAI

Upgrade Frappe to version 15.108.0 or later on the v15 branch, or to 16.18.3 or later on the v16 branch, as confirmed by the vendor in GitHub Security Advisory GHSA-3w78-3cj3-p949 at https://github.com/frappe/frappe/security/advisories/GHSA-3w78-3cj3-p949. If immediate patching is not feasible, disable the magic login link feature entirely and require password-based or OAuth authentication, which eliminates the vulnerable code path at the cost of removing passwordless login for all users. A secondary mitigation is to configure the upstream reverse proxy (e.g., nginx: proxy_set_header Host $host; Apache: ProxyPreserveHost Off with a hardcoded ServerName) to forcibly overwrite the Host header with the correct server hostname before the request reaches Frappe - however, operators should verify that Frappe reads the corrected header rather than an X-Forwarded-Host or similar pass-through header, otherwise this control may not be effective.