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

Frappe framework versions before 16.19.0 allow low-privileged users to modify shared workspaces they should not control, undermining access control governance and collaboration integrity.. A patch is available.

How to fix or mitigate CVE-2026-49394?

Within 24 hours: Inventory all Frappe instances running versions prior to 16.19.0 and identify those with shared public Workspaces. Within 7 days: Validate Frappe 16.19.0 patch in non-production environment for compatibility. Within 30 days: Deploy Frappe 16.19.0 across all production systems and review workspace modification logs for unauthorized activity.

Frappe Framework CVE-2026-49394

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

CVE-2026-49394 has a CVSS 4.0 base score of 7.1 (High). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/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.3%.

EUVD-2026-43105 HIGH

Missing Authorization (CWE-862)

2026-07-10 GitHub_M

Authentication Bypass Frappe

7.1

CVSS 4.0 · Vendor: GitHub_M

Severity by source

Vendor (GitHub_M) PRIMARY

7.1 HIGH

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/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

6.5 MEDIUM

Network-reachable endpoint (AV:N) with low complexity, but a valid low-privilege account is required (PR:L); impact is integrity-only tampering of public workspaces, so C:N/I:H/A:N.

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

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

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Patch available

Jul 10, 2026 - 23:02 EUVD

Analysis Generated

Jul 10, 2026 - 21:55 vuln.today

DescriptionCVE.org

Frappe is a full-stack web application framework. Prior to 16.19.0, authorization bypass was possible via the update_page endpoint in Workspace because public workspaces did not receive the required Workspace Manager edit check. This issue is fixed in version 16.19.0.

AnalysisAI

Broken access control in the Frappe framework (all versions prior to 16.19.0) lets a low-privileged authenticated user modify public Workspaces they should not control, because the update_page endpoint failed to enforce the Workspace Manager edit permission on public workspaces. Any user able to reach the endpoint can alter shared workspace layout and content, an integrity-only impact with no data disclosure. No public exploit has been identified, EPSS/KEV data were not provided, and the fix is shipped in Frappe 16.19.0.

Technical ContextAI

Frappe is the open-source full-stack Python/JavaScript web framework that underpins ERPNext and other business applications; Workspaces are the configurable dashboard/navigation pages that can be scoped as private (per-user) or public (shared org-wide). Editing a public Workspace is intended to be gated behind the Workspace Manager role. The flaw is a classic CWE-862 Missing Authorization: the server-side update_page handler applied the required Workspace Manager edit check for the private path but omitted it for public workspaces, so the authorization decision was incomplete. The CPE cpe:2.3:a:frappe:frappe:*:*:*:*:*:*:*:* indicates the frappe framework package itself is affected across versions up to the 16.19.0 fix.

RemediationAI

Vendor-released patch: 16.19.0 - upgrade the Frappe framework to v16.19.0 or later (https://github.com/frappe/frappe/releases/tag/v16.19.0), which adds the missing Workspace Manager edit check to the public-workspace path; the underlying fixes are in PRs https://github.com/frappe/frappe/pull/39508 and https://github.com/frappe/frappe/pull/39526 and commits 2471d94c397dc23301b30ed3bb30353f53b33f2c and 6eba29d7ae80cdb4d0b2a245a477b1d2312736ca. If immediate upgrade is not possible, reduce exposure by tightening account provisioning so that only trusted users hold authenticated sessions, and restrict or monitor access to public Workspace editing (the update_page endpoint); note that limiting who can register or authenticate is the practical compensating control since the endpoint itself cannot be safely disabled without breaking legitimate Workspace management. Review advisory GHSA-r24j-xrj8-273q for vendor guidance.