Is there a patch available for CVE-2026-47182?

Yes, a patch is available for CVE-2026-47182. Update the affected software to the latest version immediately.

Frappe Framework CVE-2026-47182

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

CVE-2026-47182 has a CVSS 4.0 base score of 5.3 (Medium). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/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. EPSS exploitation probability: 0.0%.

EUVD-2026-36495 MEDIUM

Improper Access Control (CWE-284)

2026-06-12 GitHub_M

Authentication Bypass Frappe

5.3

CVSS 4.0 · Vendor: GitHub_M

Severity by source

Vendor (GitHub_M) PRIMARY

5.3 MEDIUM

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

vuln.today AI

4.3 MEDIUM

AV:N as file access occurs over HTTP; PR:L because any valid authenticated session is required; C:L for limited file disclosure with no integrity or availability impact.

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

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

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Patch available

Jun 12, 2026 - 17:01 EUVD

Analysis Generated

Jun 12, 2026 - 16:30 vuln.today

DescriptionCVE.org

Frappe is a full-stack web application framework. Prior to version 16.17.4, any authenticated user can access private files by guessing the file path. This issue has been patched in version 16.17.4.

AnalysisAI

Improper access control in Frappe Framework (all versions prior to 16.17.4) allows any authenticated user to retrieve private files by guessing their server-side file path, bypassing intended authorization restrictions. The flaw is classified under CWE-284 (Improper Access Control) and affects the file-serving layer of the framework, which underlies widely deployed applications such as ERPNext. No public exploit code has been identified at time of analysis, and exploitation probability is very low per EPSS (0.02%, 7th percentile), though the low attack complexity makes it straightforward for any credentialed user to attempt.

Technical ContextAI

Frappe is a Python/JavaScript full-stack web framework that powers ERPNext and other enterprise applications. Its file-serving subsystem manages uploaded attachments and private documents, distinguishing between public and private files via access control policy. The root cause, CWE-284 (Improper Access Control), indicates that the application fails to enforce proper authorization checks server-side when a private file URL is directly requested - relying instead on path obscurity rather than role-based permission verification. The CPE identifier cpe:2.3:a:frappe:frappe:*:*:*:*:*:*:*:* confirms all versions of the Frappe application are affected up to the fix point. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N) corroborates a network-reachable flaw requiring only a valid authenticated session and no special attack conditions.

RemediationAI

Upgrade Frappe to version 16.17.4 or later, which contains the vendor-released patch per GitHub Security Advisory GHSA-gvg7-4p32-j648 (https://github.com/frappe/frappe/security/advisories/GHSA-gvg7-4p32-j648). If immediate patching is not feasible, implement web server or reverse-proxy rules to enforce authentication and role-based authorization checks on all requests to private file-serving endpoints, which prevents unauthenticated and cross-tenant access at the infrastructure layer - though this does not fix the application-level control gap for authenticated users across roles. Additionally, audit private file naming conventions and consider enforcing randomized, high-entropy filenames to raise the difficulty of path guessing; note this is a hardening measure, not a substitute for the patch, and does not address the architectural control failure.