CVE-2026-39352
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 · uneditedFrappe is a full-stack web application framework. Versions prior to 15.105.0 and 16.15.0 contain a possible Arbitrary File Read vulnerability via Path Traversal. The issue is resolved in versions 16.15.0, 15.105.0 and above.
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 confidenceFrappe framework versions prior to 15.105.0 and 16.15.0 contain an arbitrary file read vulnerability exploitable through path traversal. Attackers can manipulate file paths to access sensitive files outside the intended web root directory.
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
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Frappe installation existsRun 'bench version' from the Frappe bench directory, or check pip show frappe, or look for Frappe installation in the systemAffected if Frappe framework is installed on the server
-
Identify the exact Frappe versionExecute 'bench version' or 'pip show frappe' to retrieve the installed version numberAffected if The version returned is lower than 15.105.0 or 16.15.0, or falls in the range between these major versions
-
Confirm the file handling endpoint is exposedCheck if web requests to file-related routes (such as /api/method/frappe... or file download endpoints) are reachable from the network without authenticationAffected if The file handling functionality is accessible over the network without authentication
-
Verify file operations are permittedInspect whether the Frappe file handler allows arbitrary path traversal in request parameters (such as using ../ sequences in file path arguments)Affected if The file path input in the file handling functionality accepts and processes path traversal sequences
You are affected if Frappe is installed with a version prior to 15.105.0 or prior to 16.15.0 and the file handling functionality is accessible without authentication.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade Frappe to version 15.105.0 or 16.15.0 or later to resolve the path traversal vulnerability.
15.105.0 (for v15.x) or 16.15.0 (for v16.x)
- 1. Identify the currently installed Frappe version by checking the requirements.txt, bench version, or site configuration
- 2. If running Frappe version 15.x, upgrade to version 15.105.0 or later
- 3. If running Frappe version 16.x, upgrade to version 16.15.0 or later
- 4. Run database migrations after upgrade using `bench migrate` or `bench --site [site-name] migrate`
- 5. Clear cache and restart all Frappe workers/services
- 6. Verify the upgrade was successful and test that the path traversal vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-39352 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-39352 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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