CVE-2026-39351
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. Prior to 16.14.0 and 15.104.0, Frappe allows unrestricted Doctype access via API exploit.
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 · moderate confidenceFrappe framework versions prior to 16.14.0 and 15.104.0 contain an API vulnerability allowing unrestricted access to Doctype (document type) objects. This enables unauthenticated or unauthorized users to potentially read, modify, or delete data through the API by bypassing access control checks on Doctype entities.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 15.104.0>= 16.0.0, < 16.14.0CVSS 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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
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.
-
Determine installed Frappe versionRun `bench version` in the Frappe bench directory, or inspect the version file in your Frappe installation (typically at /frappe-bench/sites/[site name]/site_config.json or the Frappe package version)Affected if The reported version is less than 15.104.0, or greater than or equal to 16.0.0 but less than 16.14.0
-
Verify API endpoint exposureSend a request to an arbitrary doctype API endpoint such as `/api/resource/Doctor` or `/api/method/frappe.client.get` without providing valid authentication credentialsAffected if The API returns data or accepts operations without requiring valid session authentication (response status 200 instead of 401/403)
Your environment is affected if the Frappe installation version falls within the vulnerable ranges (< 15.104.0 or >= 16.0.0 and < 16.14.0) AND the REST API is accessible without proper 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 · scoped15.104.016.14.0
Upgrade Frappe to version 16.14.0 or 15.104.0 or later. After upgrading, audit API access controls and review user/role permissions for all custom Doctypes to ensure proper restrictions are in place.
Upgrade to Frappe 15.104.0 (for 15.x users) or Frappe 16.14.0 (for 16.x users)
- 1. Identify the current Frappe version by running 'bench version' or checking the version file
- 2. For Frappe 15.x versions: Upgrade to version 15.104.0 using 'bench get-app frappe --version 15.104.0' or equivalent upgrade command
- 3. For Frappe 16.x versions: Upgrade to version 16.14.0 using 'bench get-app frappe --version 16.14.0' or equivalent upgrade command
- 4. Run 'bench migrate' to apply any database migrations after the upgrade
- 5. Restart all Frappe bench processes (bench restart or equivalent)
- 6. Verify the upgrade was successful by checking 'bench version' and testing that API access controls are properly enforced
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
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 locallyCheck whether your project pulls in CVE-2026-39351 — 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-39351 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