dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2026-47182

MEDIUM · 5.3 CVSS v4.0 Published 2026-06-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Frappe framework prior to version 16.17.4 contains an Insecure Direct Object Reference (IDOR) vulnerability allowing any authenticated user to access private files by guessing file paths, due to insufficient authorization checks on file access endpoints.

MitigationUpgrade to Frappe version 16.17.4 or later to apply the patched authorization logic for file access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Frappe version
    Run 'bench version' in the Frappe/ERPNext bench directory, or check the version file in the Frappe installation (typically in /frappe-bench/sites/[site-name]/frappe-benchmark or the Frappe package.json)
    Affected if The installed version is below 16.17.4 (e.g., 16.17.3, 16.16.0, etc.)
  2. Verify authenticated user can access file API
    Using an authenticated session (as a standard user with no file access permissions), attempt a GET request to the file access endpoint (typically /api/method/frappe.handler.upload_file or /api/files/[path]) with a guessed private file path
    Affected if The request returns file contents or metadata for a file that should be private or inaccessible to that user
  3. Test IDOR on file download endpoint
    As a low-privilege authenticated user, send a request to the file download endpoint (commonly /api/method/frappe.utils.file_manager.download_file) with a file path to a private file (such as /private/files/confidential.pdf) that you do not own
    Affected if The system returns the file content without enforcing ownership or permission checks, indicating the IDOR is present
  4. Check authorization middleware on file endpoints
    Inspect the Frappe source code in the file_manager.py or handler.py module for the download_file and related functions. Look for permission checks (like has_permission or validate_file_owner) before serving file content
    Affected if The code lacks or bypasses authorization checks before returning file data, allowing any authenticated user to retrieve files by path

A user is affected if their Frappe installation is version 16.17.3 or earlier and the file access endpoints permit unaudited access to private files by authenticated users without proper ownership verification.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Frappe version 16.17.4 or later to apply the patched authorization logic for file access.

Recommended fix High confidence

version 16.17.4

  1. Backup your current Frappe installation and database before upgrading
  2. Update your Frappe installation to version 16.17.4 or later
  3. Verify the fix by confirming that private files are no longer accessible through guessed file paths
  4. After upgrading, test that authenticated users can only access files they are explicitly authorized to view

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47182 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-47182 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data